Extended asynchronous data mover functions compatibility indication

ABSTRACT

A method is provided that is executable by a processor of a computer. Note that the processor is communicatively coupled to a memory of the computer, and the memory stores a response block of a call command. In implementing the method, the processor defines a sub-functions field in the response block of the call command. Further the processor indicates that a set of functions of a set of instructions are installed and available at an interface based on a corresponding sub-functions flag within the sub-functions field being set. Note that the interface is also being executed on the computer and that the set of functions being represented by the corresponding sub-functions flag. The processor further indicates that the set of functions of the set of instructions are not installed based on the corresponding sub-functions flag not being set.

BACKGROUND

One or more aspects of the present invention relate, in general, toinstructions of a computing environment, and in particular, to managingextended asynchronous data mover (EADM) functions compatibilityindication.

A set of new instructions and/or new functions are generally controlledby a single facility flag. If the flag is set, then the set of newinstructions and/or new functions that are controlled by that facilityflag are installed on a machine model where software is running, andthus are available for use by the software. Otherwise, the set of newinstructions and/or new functions that are controlled by that facilityflag are not installed on the machine model where the software isrunning and cannot be used by the software.

Furthermore, a new instruction may not provide all the supportedfunctions on a machine model based on the machine model's setting orcapability. Therefore, the machine needs to provide a method to enableor disable one or more functions of the new instruction based on themachine model's setting or capability. To accomplish this, the newinstruction may provide a query function to the software. Then thesoftware can issue this query function to determine which otherfunctions of the new instruction are supported on the machine modelwhere the software is running.

However, there are cases where only a specific set of new instructionsand/or new functions of the first machine architecture using the firstmachine interface are also used by another (second) machine architecturebecause the second machine architecture uses a different (second)machine interface. This second machine interface may not have access tothe new instruction's query function directly or using the newinstruction's query function directly to obtain the installed andavailable functions may not be the best option.

SUMMARY

In accordance with one or more embodiments, a method is provided that isexecutable by a processor of a computer. Note that the processor iscommunicatively coupled to a memory of the computer, and the memorystores a response block of a call command. In implementing the method,the processor defines a sub-functions field in the response block of thecall command. Further the processor indicates that a set of functions ofa set of instructions are installed and available at an interface basedon a corresponding sub-functions flag within the sub-functions fieldbeing set. Note that the interface is also being executed on thecomputer and that the set of functions being represented by thecorresponding sub-functions flag. The processor further indicates thatthe set of functions of the set of instructions are not installed basedon the corresponding sub-functions flag not being set. The technicaleffects and benefits of the one or more embodiments herein allow newextended asynchronous data mover (EADM) commands that belong to anexisting EADM feature and to be added to an existing EADM featurewithout requiring a new EADM feature for the new EADM commands.

In accordance with one or more embodiments or the method embodimentabove, the sub-functions field can include an EADM sub-functions field.

In accordance with one or more embodiments or any of the methodembodiments above, the call command can include a store EADM informationchannel subsystem call command.

In accordance with one or more embodiments or any of the methodembodiments above, the sub-functions flag can include an EADMsub-functions flag.

In accordance with one or more embodiments or any of the methodembodiments above, the interface can include an EADM interface. Thetechnical effects and benefits of the one or more embodiments hereinprovide better features, instructions and functions grouping, and usesless functions definition space to determine the EADM commands validity.

In accordance with one or more embodiments or any of the methodembodiments above, each bit in the sub-functions field can represent oneor more of the set of functions that are installed and available at theinterface.

In accordance with one or more embodiments or any of the methodembodiments above, the set of functions of the set of instructions canbe of a first machine being executed on the computer, and the interfacecan be a second machine.

In accordance with one or more embodiments or any of the methodembodiments above, the set of functions may not be usable by theinterface based on the set of functions of the set of instructionsrepresented by the sub-functions flag not being installed.

In accordance with one or more embodiments or any of the methodembodiments above, a facility can use the interface to execute the setof instructions with a subset of functions via a system assistanceprocessor of the computer. The technical effects and benefits of the oneor more embodiments herein simplifies hardware, SAP and software design,and reduces hardware and software processing time to determine the EADMcommands validity.

In accordance with one or more embodiments or any of the methodembodiments above, the facility can contain a set of managing extendedasynchronous data mover (EADM) features and each one of these featuresincludes a set of EADM commands.

In accordance with one or more embodiments or any of the methodembodiments above, each command of the set of EADM commands can use oneor more of the set of instructions and corresponding functions tocomplete a task.

The above described features of the one or more method embodiments canalso be provided at least by a system, a computer program product, and amachine.

Additional technical features and benefits are realized through thetechniques of the present invention. Embodiments and aspects of theinvention are described in detail herein and are considered a part ofthe claimed subject matter. For a better understanding, refer to thedetailed description and to the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The specifics of the exclusive rights described herein are particularlypointed out and distinctly claimed in the claims at the conclusion ofthe specification. The foregoing and other features and advantages ofthe embodiments of the invention are apparent from the followingdetailed description taken in conjunction with the accompanying drawingsin which:

FIG. 1A depicts one example of a computing environment to incorporateand use one or more aspects of the present invention;

FIG. 1B depicts further details of a processor of FIG. 1A, in accordancewith one or more aspects of the present invention;

FIG. 2 depicts another example of a computing environment to incorporateand use one or more aspects of the present invention;

FIG. 3A depicts one format of a DEFLATE Conversion Call (DFLTCC)instruction, in accordance with an aspect of the present invention;

FIG. 3B depicts one example of fields of an implied register, generalregister 0, used by the DEFLATE Conversion Call instruction, inaccordance with an aspect of the present invention;

FIG. 3C depicts one example of function codes for the DEFLATE ConversionCall instruction, in accordance with an aspect of the present invention;

FIG. 3D depicts one example of a field of an implied register, generalregister 1, used by the DEFLATE Conversion Call instruction, inaccordance with an aspect of the present invention;

FIG. 3E depicts one example of contents of a register, R1, specified bythe DEFLATE Conversion Call instruction, in accordance with an aspect ofthe present invention;

FIG. 3F depicts one example of contents of a register, R1+1, used by theDEFLATE Conversion Call instruction, in accordance with an aspect of thepresent invention;

FIG. 3G depicts one example of contents of a register, R2, specified bythe DEFLATE Conversion Call instruction, in accordance with an aspect ofthe present invention;

FIG. 3H depicts one example of contents of a register, R2+1, used by theDEFLATE Conversion Call instruction, in accordance with an aspect of thepresent invention;

FIG. 3I depicts one example of contents of a register, R3, specified bythe DEFLATE Conversion Call instruction, in accordance with an aspect ofthe present invention;

FIG. 3J depicts one example of contents of a parameter block used by theDFLTCC-QAF (query available functions) function of the DEFLATEConversion Call instruction, in accordance with an aspect of the presentinvention;

FIG. 3K depicts one example of contents of a parameter block used by theDFLTCC-GDHT (generate dynamic-Huffman table) function of the DEFLATEConversion Call instruction, in accordance with an aspect of the presentinvention;

FIG. 3L depicts one example of contents of a parameter block used by theDFLTCC-CMPR (compress) and DFLTCC-XPND (expand) functions of the DEFLATEConversion Call instruction, in accordance with an aspect of the presentinvention;

FIG. 4 depicts one example of a sub-byte boundary, in accordance withone or more aspects of the present invention;

FIGS. 5A-5C depict examples illustrating how a sub-byte boundary appliesto the DFTLCC-CMPR function, in accordance with an aspect of the presentinvention;

FIG. 6 depicts one example of a block of data with no compression, inaccordance with an aspect of the present invention;

FIG. 7 depicts one example of a block with compressed data using afixed-Huffman table (FHT), in accordance with an aspect of the presentinvention;

FIG. 8 depicts one example of a block with compressed data using adynamic-Huffman table (DHT), in accordance with an aspect of the presentinvention;

FIG. 9 depicts one example of a compressed data set in storage, inaccordance with an aspect of the present invention;

FIG. 10 depicts one example of a sample of a program compressing datainto three blocks of a compressed data set, in accordance with an aspectof the present invention;

FIG. 11 depicts one example of parameter block contents for aDFLTCC-CMPR function operating on a first compressed data block of aset, in accordance with an aspect of the present invention;

FIG. 12 depicts one example of parameter block contents for aDFLTCC-CMPR function operating on a second compressed data block of aset, in accordance with an aspect of the present invention;

FIG. 13 depicts one example of a sample of a program decompressing datafrom a compressed data set, in accordance with an aspect of the presentinvention;

FIGS. 14A-14C depict examples of an in-line history buffer before andafter executing DFLTCC-CMPR multiple times, in accordance with an aspectof the present invention;

FIGS. 15A-15E depict examples of a circular history buffer before andafter executing DFLTCC multiple times, in accordance with an aspect ofthe present invention;

FIGS. 16A-16C depict examples of an in-line history buffer before andafter executing DFLTCC-XPND multiple times, in accordance with an aspectof the present invention;

FIG. 17 depicts one example of using the DEFLATE Conversion Callinstruction, in accordance with an aspect of the present invention;

FIG. 18 depicts one example of using a circular history buffer, inaccordance with an aspect of the present invention;

FIG. 19 depicts a computing environment in accordance with one or moreembodiments;

FIG. 20 depicts a computing environment in accordance with one or moreembodiments;

FIG. 21 depicts a process flow in accordance with one or moreembodiments; and

FIG. 22 depicts a format of command-response block for store EADMinformation in accordance with one or more embodiments.

DETAILED DESCRIPTION

As discussed above, there are cases where only a specific set of newinstructions and/or new functions of the first machine architectureusing the first machine interface are also used by another (second)machine architecture. This second machine interface may not have accessto the query function to obtain the installed and available functions.

According to one or more embodiments herein, to solve this problem, theinvention provides a validity of certain functions that would be used bythe EADM interface to execute one of those functions if it is indicatedto be valid through our invention. For example, a computer or a machine(e.g., CPU) provides a mechanism to indicate if the set of newinstructions and/or new functions of a first machine interface that areneeded by an EADM (e.g., second machine) interface are also installedand available at the second machine interface. Herein, a new EADM(enhanced asynchronous data mover) sub-functions field is defined in aresponse block of a store EADM information channel subsystem call (CHSC)command and each bit (e.g., flag) in this EADM sub-functions fieldrepresents one or more functions of one or more instructions that areinstalled and available at the EADM interface. As noted, the EADMsub-functions field can include bits or flags, which can be referred toas EADM sub-functions flags.

In accordance with one or more embodiments, if an EADM sub-functionsflag is set, then the set of functions of the set of instructions thatare represented by that EADM sub-functions flag are installed andavailable at the EADM interface of the machine model where the softwareis running. Further, if the EADM sub-functions flag is set, then the setof functions are available to a system assistance processor (SAP) andsoftware to take advantage of those installed set of functions of theset of instructions. Otherwise, the set of functions of the set ofinstructions that are represented by that EADM sub-functions flag arenot installed on the machine model where the software is running andcannot be used by the SAP or the software.

In accordance with one or more embodiments, similar functionality can beprovided by utilizing a list of actual instruction codes or mnemonicsand their function codes or mnemonics. Utilizing this list would requiresetting aside a number of bytes for future expansion in the responseblock of the store EADM information CHSC command to contain all thecurrent and future instruction codes or mnemonics and their functioncodes or mnemonics. In addition, additional hardware and SAP or softwarecode would be leveraged to implement and traverse through this list ofinstruction codes or mnemonics and their function codes or mnemonics todetermine if the required instructions and their functions are installedand available at the EADM interface of the machine model where thesoftware is running.

One embodiment of a computing environment to incorporate and use one ormore aspects of the present invention is described with reference toFIG. 1A. A computing environment 100 includes, for instance, a processor102 (e.g., a central processing unit), a memory 104 (e.g., main memory;a.k.a., system memory, main storage, central storage, storage), and oneor more input/output (I/O) devices and/or interfaces 106 coupled to oneanother via, for example, one or more buses 108 and/or otherconnections.

In one example, processor 102 is based on the z/Architecture® hardwarearchitecture offered by International Business Machines Corporation,Armonk, N.Y., and is part of a server, such as an IBM Z® server, whichis also offered by International Business Machines Corporation andimplements the z/Architecture hardware architecture. One embodiment ofthe z/Architecture hardware architecture is described in a publicationentitled, “z/Architecture Principles of Operation,” IBM Publication No.SA22-7832-11, 12th edition, September 2017, which is hereby incorporatedherein by reference in its entirety. The z/Architecture hardwarearchitecture, however, is only one example architecture; otherarchitectures and/or other types of computing environments may includeand/or use one or more aspects of the present invention. In one example,the processor executes an operating system, such as the z/OS® operatingsystem, also offered by International Business Machines Corporation.

Processor 102 includes a plurality of functional components used toexecute instructions. As depicted in FIG. 1B, these functionalcomponents include, for instance, an instruction fetch component 120 tofetch instructions to be executed; an instruction decode unit 122 todecode the fetched instructions and to obtain operands of the decodedinstructions; an instruction execute component 124 to execute thedecoded instructions; a memory access component 126 to access memory forinstruction execution, if necessary; and a write back component 130 toprovide the results of the executed instructions. One or more of thesecomponents may, in accordance with one or more aspects of the presentinvention, include at least a portion of or have access to one or moreother components used in compress/decompress processing (or otherprocessing that may use one or more aspects of the present invention),as described herein. The one or more other components include, forinstance, a compress/decompress component (or other component) 136.

Another example of a computing environment to incorporate and use one ormore aspects of the present invention is described with reference toFIG. 2. In one example, the computing environment is based on thez/Architecture hardware architecture; however, the computing environmentmay be based on other architectures offered by International BusinessMachines Corporation or others.

Referring to FIG. 2, in one example, the computing environment includesa central electronics complex (CEC) 200. CEC 200 includes a plurality ofcomponents, such as, for instance, a memory 202 (a.k.a., system memory,main memory, main storage, central storage, storage) coupled to one ormore processors (a.k.a., central processing units (CPUs)) 204, and to aninput/output subsystem 206.

Memory 202 includes, for example, one or more logical partitions 208, ahypervisor 210 that manages the logical partitions, and processorfirmware 212. One example of hypervisor 210 is the ProcessorResource/System Manager (PR/SM™) hypervisor, offered by InternationalBusiness Machines Corporation, Armonk, N.Y. As used herein, firmwareincludes, e.g., the microcode of the processor. It includes, forinstance, the hardware-level instructions and/or data structures used inimplementation of higher level machine code. In one embodiment, itincludes, for instance, proprietary code that is typically delivered asmicrocode that includes trusted software or microcode specific to theunderlying hardware and controls operating system access to the systemhardware.

Each logical partition 208 is capable of functioning as a separatesystem. That is, each logical partition can be independently reset, runa guest operating system 220 such as a z/OS operating system, or anotheroperating system, and operate with different programs 222. An operatingsystem or application program running in a logical partition appears tohave access to a full and complete system, but in reality, only aportion of it is available.

Memory 202 is coupled to processors (e.g., CPUs) 204, which are physicalprocessor resources that may be allocated to the logical partitions. Forinstance, a logical partition 208 includes one or more logicalprocessors, each of which represents all or a share of a physicalprocessor resource 204 that may be dynamically allocated to the logicalpartition.

Further, memory 202 is coupled to I/O subsystem 206. I/O subsystem 206may be a part of the central electronics complex or separate therefrom.It directs the flow of information between main storage 202 andinput/output control units 230 and input/output (I/O) devices 240coupled to the central electronics complex.

Many types of I/O devices may be used. One particular type is a datastorage device 250. Data storage device 250 may store one or moreprograms 252, one or more computer readable program instructions 254,and/or data, etc. The computer readable program instructions may beconfigured to carry out functions of embodiments of aspects of theinvention.

As one example, each processor 204 includes at least one cache 260(e.g., a local cache) of a cache hierarchy that includes a plurality oflevels of cache, including one or more local caches and/or one or moreshared caches. Further, in one embodiment, the local caches and memory202 are coupled to a compress/decompress component (or other component)262 used in performing one or more of compressing and/or decompressingof data (and/or other operations of one or more aspects of the presentinvention). In various examples, there may be one or more componentsperforming these tasks. Many variations are possible.

In one embodiment, a processor (e.g., processor 204) obtains theinstruction (e.g., the DEFLATE Conversion Call instruction), decodes theinstruction, performs set-up for the instruction, including translatingaddresses to be used by the instruction, and sends commands for theinstruction to a component coupled to the processor, such as component262, to perform a function specified by the instruction. Component 262has access to the cache hierarchy and memory, such that in performingthe specified function, it reads data, processes it and stores theprocessed data back. As an example, component 262 is a hardwarecomponent.

In a further embodiment, at least a portion of component 262 is includedas part of the processor. Many variations are possible.

Central electronics complex 200 may include and/or be coupled toremovable/non-removable, volatile/non-volatile computer system storagemedia. For example, it may include and/or be coupled to a non-removable,non-volatile magnetic media (typically called a “hard drive”), amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and/or an opticaldisk drive for reading from or writing to a removable, non-volatileoptical disk, such as a CD-ROM, DVD-ROM or other optical media. Itshould be understood that other hardware and/or software componentscould be used in conjunction with central electronics complex 200.Examples include, but are not limited to: microcode, device drivers,redundant processing units, external disk drive arrays, RAID systems,tape drives, and data archival storage systems, etc.

Further, central electronics complex 200 may be operational withnumerous other general purpose or special purpose computing systemenvironments or configurations. Examples of well-known computingsystems, environments, and/or configurations that may be suitable foruse with central electronics complex 200 include, but are not limitedto, personal computer (PC) systems, server computer systems, thinclients, thick clients, handheld or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Although various examples of computing environments are describedherein, one or more aspects of the present invention may be used withmany types of environments. The computing environments provided hereinare only examples.

In accordance with an aspect of the present invention, a computingenvironment, such as computing environment 100 or central electronicscomplex 200, employs a conversion facility that provides a mechanism tocompress and decompress data. In one example, the conversion facility isa DEFLATE conversion facility that provides a mechanism to compress anddecompress data using the DEFLATE compressed data format. In oneexample, the conversion facility is installed in the system when afacility indicator is set, e.g., to one. As one particular example ofthe z/Architecture hardware architecture, facility bit 151 is set to,e.g., one, when the conversion facility is installed in thez/Architecture architectural mode. The facility includes, for instance,the DEFLATE Conversion Call instruction, an embodiment of which isdescribed below.

In one example, the DEFLATE Conversion Call instruction performsfunctions related to transforming the state of data between the original(uncompressed) form of the data, and a compressed representation of thedata, as specified by a selected standard, such as the IETF (InternetEngineering Task Force) RFC (Request for Comments) 1951 specification,which is described in the DEFLATE Compressed Data Format Specificationversion 1.3 Internet Engineering Task Force, Request for Comments 1951,May 1996.

In one example, the uncompressed data is a sequence of bytes, and thecompressed representation of the data includes symbols. Symbolsrepresent an individual byte of uncompressed data, referred to as aliteral byte, or represent a reoccurring sequence of bytes ofuncompressed data, referred to as a duplicate string. A Huffman table,as an example, specifies the encoding and decoding between compresseddata symbols and uncompressed data. There are two types of Huffmantables: a fixed-Huffman table (FHT), which is a predeterminedspecification which includes, for instance, all possible codings; and adynamic-Huffman table (DHT), which is a set of codings createdspecifically for the data to be compressed, which may be a subset of allpossible codings. A compressed representation of data generated with aDHT is typically smaller than a compressed representation of the samedata generated with an FHT. A portion of the most recently processeduncompressed data, referred to as history, is maintained for encodingand decoding compressed data symbols representing duplicate strings. Thehistory is the reference source for duplicate strings. The history isupdated as data is processed during an operation.

As indicated, in one example, the DEFLATE Conversion Call instructionuses the DEFLATE compressed data format, which is described in RCF 1951,DEFLATE Compressed Data Format Specification version 1.3. Attributes ofthe DEFLATE standard which apply to the DEFLATE Conversion Callinstruction include, for instance:

-   -   A compressed data set includes a series of blocks. There are        three types of blocks. One type includes a 3-bit header followed        by length information and uncompressed data, and two types of        blocks include a 3-bit header followed by compressed data        elements.    -   Compressed data elements may include a compressed representation        of a dynamic-Huffman table, compressed data symbols, and an        end-of-block (EOB) symbol.    -   Compressed data elements have various bit lengths.    -   Compressed data elements may begin or end between byte        boundaries in storage.    -   Compressed data elements are loaded into bytes in order from,        e.g., the rightmost bit position to the leftmost bit position.

When a compressed data element occupies part of, and not all of, a bytein storage, the entire byte in storage is accessed. Storage operandlengths specify the number of addressable bytes, which may specify morebits than the compressed data occupies.

Additional details regarding compressed data blocks are describedfurther below.

One embodiment of the DEFLATE Conversion Call (DFLTCC) instruction isdescribed with reference to FIGS. 3A-3L. The instruction is executed, inone example, using a general-purpose processor (e.g., processor 102 or204). In the description herein, specific locations, specific fieldsand/or specific sizes of the fields are indicated (e.g., specific bytesand/or bits). However, other locations, fields and/or sizes may beprovided. Further, although the setting of a bit to a particular value,e.g., one or zero, is specified, this is only an example. The bit may beset to a different value, such as the opposite value or to anothervalue, in other examples. Many variations are possible.

In one embodiment, a program (e.g., an operating system or user program)may execute the DEFLATE Conversion Call instruction multiple times tocompress or uncompress a single data stream. For instance, when anapplication compresses or decompresses a large data stream (e.g.,greater than 1 M-bytes), the operation may include multiple calls tocompress or decompress buffered portions of the data stream. Inaccordance with one aspect of the present invention, a program declaresa buffer (e.g., a 32 K-byte buffer), which is used to accumulate thehistory of uncompressed data processed during an operation which spansmultiple executions of the DEFLATE Conversion Call instruction. Thebuffer is referred to as a circular history buffer, which is definedusing the DEFLATE Conversion Call instruction, as described herein.

Referring to FIG. 3A, in one example, a format of a DEFLATE ConversionCall (DFLTCC) instruction 300 is an RRF format that denotes a registerand register operation with an extended operation code (opcode) fieldand an additional register field. As an example, the instructionincludes an operation code field 302 (e.g., bits 0-15) having anoperation code indicating a DEFLATE Conversion Call operation; a firstregister field (R1) 304 (e.g., bits 24-27) designating a first pair ofgeneral registers; a second register field (R2) 306 (e.g., bits 28-31)designating a second pair of general registers; and a third registerfield (R3) 308 (e.g., bits 16-19) designating a third general register.The contents of a register designated by R1 field 304 specify a locationof a first operand (in storage); the contents of a register designatedby R2 field 306 specify a location of a second operand (in storage); andthe contents of a register designated by R3 field 308 specify a locationof a third operand (in storage). The contents of R1+1 specify the lengthof the first operand, and the contents of R2+1 specify the length of thesecond operand. In one example, bits 20-23 of the instruction arereserved and should contain zeros; otherwise, the program may notoperate compatibly in the future. As used herein, the program is the oneissuing the DEFLATE Conversion Call instruction. It may be a userprogram, an operating system or another type of program.

In one embodiment, execution of the instruction includes the use of oneor more implied general registers (i.e., registers not explicitlydesignated by the instruction). For instance, general registers 0 and 1are used in execution of the DEFLATE Conversion Call instruction, asdescribed herein. General register 0 is used, in one example, to specifya function to be performed (as well as a history buffer type, describedbelow), and general register 1 is used to provide a location of aparameter block used by the instruction.

As an example, with reference to FIG. 3B, a general register 0 (309)includes a history buffer type field 310 and a function code field 312.In one particular example, bit position 56 of general register 0includes a history buffer type, and bit positions 57-63 of generalregister 0 contain a function code; but in other embodiments, other bitsmay be used to contain the history buffer type and/or the function code.When bits 57-63 of general register 0 designate an unassigned oruninstalled function code, a specification exception is recognized, inone example.

Example assigned function codes for the DEFLATE Conversion Callinstruction are shown in FIG. 3C and include, for instance: functioncode 0 (313) indicating a DFLTCC-QAF (query available functions)function; function code 1 (315) indicating a DFLTCC-GDHT (GenerateDynamic-Huffman Table) function; function code 2 (317) indicating aDFLTCC-CMPR (compress) function; and function code 4 (319) indicating aDFLTCC-XPND (expand) function. Each code uses a parameter block and thesize of the parameter block depends, in one example, on the function.For instance, for the DFLTCC-QAF function, the parameter block is 32bytes; for the DFLTCC-GDHT function, the parameter block is 384 bytes;and for the DFLTCC-CMPR and DFLTCC-XPND functions, the parameter blockis 1536 bytes. Other function codes are unassigned in this example.Although example functions and function codes are described, otherfunctions and/or function codes may be used.

When the specified function is DFLTCC-CMPR or DFLTCC-XPND, bit 56 ofgeneral register 0 specifies the history buffer type (HBT) used duringthe operation. When HBT is zero, the history buffer is called an in-linehistory buffer. When using an in-line history buffer, the history is,e.g., immediately to the left of the second operand when DFLTCC-CMPR isspecified and is, e.g., immediately to the left of the first operandwhen DFLTCC-XPND is specified. When HBT is one, the history buffer iscalled a circular history buffer. When using a circular history buffer,the history is a portion of, or all of, the third operand when eitherDFLTCC-CMPR or DFLTCC-XPND is specified. When the DFLTCC-QAF orDFLTCC-GDHT function is specified, bit 56 of general register 0 isignored. In one example, bit positions 0-31 of general register 0 areignored. Further, in one example, bit positions 32-55 of generalregister 0 are reserved and should contain zeros; otherwise, the programmay not operate compatibly in the future.

Further details regarding another implied register, general register 1,used by the DEFLATE Conversion Call instruction are described withreference to FIG. 3D. The contents of general register 1 (314) specify,for instance, a logical address 316 of the leftmost byte of a parameterblock in storage. The parameter block is to be designated on a 4K-byteboundary, in one example; otherwise a specification exception isrecognized. Further details regarding the parameter block are describedfurther below.

For the specified functions (e.g., DFLTCC-QAF, DFLTCC-GDHT, DFLTCC-CMPR,DFLTCC-XPND), the contents of general registers 0, 1 and R3 are notmodified. Further, in one example, R1 field 304 designates an even-oddpair of general registers. It is to designate an even-numbered registerand is not to designate general register 0; otherwise, a specificationexception is recognized.

As depicted in FIGS. 3E-3F and described in further detail herein, thecontents of general register R1 318 indicate a first operand address320, and the contents of general register R1+1 322 are used to determinethe length 324 of the first operand. For instance, when the specifiedfunction is DFLTCC-CMPR or DFLTCC-XPND, the contents of general registerR1 318 specify a logical address of the leftmost byte of the firstoperand. When the specified function is DFLTCC-CMPR, the contents ofgeneral register R1+1, in conjunction with the values of the new task(NT) and sub-byte boundary (SBB) fields of the parameter block(described below), specify the length of the first operand. Thefollowing table provides examples which demonstrate the length of thefirst operand for the DFLTCC-CMPR function as a function of the contentsof general register R1+1, the NT field, and the SBB field:

SBB Length of First Contents of GR R1 + 1 (hex) NT (binary) Operand00000000 00000002 0 001 15 bits 00000000 00000001 1 — 8 bits 0000000000000001 0 000 8 bits 00000000 00000001 0 011 5 bits 00000000 00000001 0111 1 bit 00000000 00000000 — — 0 bits

When the specified function is DFLTCC-XPND, the contents of generalregister R1+1 specify the length of the first operand. When thespecified function is DFLTCC-CMPR or DFLTCC-XPND, the results ofcompressing or decompressing data are stored at the first operandlocation. When the DFLTCC-QAF or DFLTCC-GDHT function is specified, thecontents of general registers R1 and R1+1 are ignored.

Moreover, for the specified functions (e.g., DFLTCC-QAF, DFLTCC-GDHT,DFLTCC-CMPR and DFLTCC-XPND), in one example, R2 field 306 designates aneven-odd pair of general registers. It is to designate an even-numberedregister and is not to designate general register 0; otherwise, aspecification exception is recognized.

As depicted in FIGS. 3G-3H and described in further detail herein, thecontents of general register R2 326 indicate a second operand address328, and the contents of general register R2+1 330 are used to determinethe length 332 of the second operand. For instance, when the specifiedfunction is DFLTCC-GDHT, DFLTCC-CMPR, or DFLTCC-XPND, the contents ofgeneral register R2 specify a logical address of the leftmost byte ofthe second operand. When the specified function is DFLTCC-CMPR orDFLTCC-GDHT, the contents of general register R2+1 specify the length ofthe second operand. When the specified function is DFLTCC-XPND, thecontents of general register R2+1, in conjunction with the values of theNT and SBB fields of the parameter block, specify the length of thesecond operand. When the second operand length is referenced and has anon-zero value at the beginning of the execution of the instruction,data is fetched from the second operand location. When the secondoperand length is referenced, has a value of zero at the beginning ofthe execution of the instruction, and the continuation flag (CF) fieldof the parameter block is one at the beginning of the execution of theinstruction, the second operand is not accessed.

When the DFLTCC-QAF function is specified, the contents of generalregisters R2 and R2+1 are ignored. When the DFLTCC-GDHT function isspecified and the contents of general register R2+1 specify a lengthequal to zero, a specification exception is recognized, and the secondoperand is not accessed. When the DFLTCC-CMPR or DFLTCC-XPND function isspecified, the continuation flag (CF) field of the parameter block iszero at the beginning of the execution of the instruction, and thecontents of general register R2+1 specify a length equal to zero, aspecification exception is recognized, and the second operand is notaccessed.

As shown in FIG. 3I, when the specified function is DFLTCC-CMPR orDFLTCC-XPND and the history buffer type (HBT) is circular (e.g. HBT310=1), the contents of general register R3 335 specify a circularhistory buffer address 337. For instance, a logical address of theleftmost byte of the third operand is specified. It is to designate,e.g., a 4 K-byte boundary; otherwise a specification exception isrecognized. In one example, the circular history buffer is located atthe third operand location. When the specified function is DFLTCC-CMPRor DFLTCC-XPND and the HBT is zero, the contents of general register R3are ignored. When the DFLTCC-QAF or DFLTCC-GDHT function is specified,the contents of general register R3 are ignored. For the specifiedfunctions (e.g., DFLTCC-QAF, DFLTCC-GDHT, DFLTCC-CMPR and DFLTCC-XPND),the R3 field is not to designate general register 0 or general register1; otherwise, a specification exception is recognized, in one example.

As part of the operation, when the specified function is DFLTCC-CMPR,the address in general register R1 is incremented by the number of bytesprocessed of the first operand that included processing bit position 0,and the length in general register R1+1 is decremented by the samenumber; the address in general register R2 is incremented by the numberof bytes processed of the second operand, and the length in generalregister R2+1 is decremented by the same number. The number of bytesprocessed of the first operand that included processing bit position 0is, for instance, the integer quotient resulting from an integerdivision with the dividend being the sum of the number of output bitsprocessed and the original value of the SBB, and the divisor being avalue of eight. The formation and updating of the addresses and lengthsare dependent on the addressing mode, as described below.

As part of the operation, when the specified function is DFLTCC-XPND,the address in general register R1 is incremented by the number of bytesprocessed of the first operand, and the length in general register R1+1is decremented by the same number; the address in general register R2 isincremented by the number of bytes processed of the second operand thatincluded processing bit position 0, and the length in general registerR2+1 is decremented by the same number. The number of bytes processed ofthe second operand that included processing bit position 0 is theinteger quotient resulting from an integer division with the dividendbeing the sum of the number of input bits processed and the originalvalue of the SBB, and the divisor being a value of eight. The formationand updating of the addresses and lengths are dependent on theaddressing mode, as described below.

In the 24-bit addressing mode, the following apply, in one embodiment:

-   -   The contents of bit positions 40-63 of general registers 1, R1,        R2, and R3 constitute the addresses of the parameter block,        first operand, second operand, and circular history buffer,        respectively, and the contents of bit positions 0-39 are        ignored.    -   Bits 40-63 of the updated first operand and second operand        addresses replace the corresponding bits in general registers R1        and R2, respectively. Carries out of bit position 40 of the        updated addresses are ignored, and the contents of bit positions        32-39 of general registers R1 and R2 are set to zeros. The        contents of bit positions 0-31 of general registers R1 and R2        remain unchanged. When the instruction ends with partial or        normal completion, and an updated operand address equals the        operand address at the beginning of execution of the        instruction, bit positions 32-39 of the corresponding general        register are set to zeros.    -   The contents of bit positions 32-63 of general registers R1+1        and R2+1 form, e.g., 32-bit unsigned binary integers which        specify the number of bytes in the first and second operands,        respectively. The contents of bit positions 0-31 of general        registers R1+1 and R2+1 are ignored.    -   Bits 32-63 of the updated first operand and second operand        lengths replace the corresponding bits in general registers R1+1        and R2+1, respectively. The contents of bit positions 0-31 of        general registers R1+1 and R2+1 remain unchanged.

In the 31-bit addressing mode, the following apply, in one embodiment:

-   -   The contents of bit positions 33-63 of general registers 1, R1,        R2, and R3 constitute the addresses of the parameter block,        first operand, second operand, and circular history buffer,        respectively, and the contents of bit positions 0-32 are        ignored.    -   Bits 33-63 of the updated first operand and second operand        addresses replace the corresponding bits in general registers R1        and R2, respectively. Carries out of bit position 33 of the        updated addresses are ignored, and the content of bit position        32 of general registers R1 and R2 is set to zero. The contents        of bit positions 0-31 of general registers R1 and R2 remain        unchanged. When the instruction ends with partial or normal        completion, and an updated operand address equals the operand        address at the beginning of the execution of the instruction,        bit position 32 of the corresponding general register is set to        zero.    -   The contents of bit positions 32-63 of general registers R1+1        and R2+1 form 32-bit unsigned binary integers which specify the        number of bytes in the first and second operands, respectively.        The contents of bit positions 0-31 of general registers R1+1 and        R2+1 are ignored.    -   Bits 32-63 of the updated first operand and second operand        lengths replace the corresponding bits in general registers R1+1        and R2+1, respectively. The contents of bit positions 0-31 of        general registers R1+1 and R2+1 remain unchanged.

In the 64-bit addressing mode, the following apply, in one embodiment:

-   -   The contents of bit positions 0-63 of general registers 1, R1,        R2, and R3 constitute the addresses of the parameter block,        first operand, second operand, and circular history buffer,        respectively.    -   Bits 0-63 of the updated first operand and second operand        addresses replace the corresponding bits in general registers R1        and R2, respectively. Carries out of bit position 0 of the        updated addresses are ignored.    -   The contents of bit positions 0-63 of general registers R1+1 and        R2+1 form 64-bit unsigned binary integers which specify the        number of bytes in the first and second operands, respectively.    -   Bits 0-63 of the updated first operand and second operand        lengths replace the corresponding bits in general registers R1+1        and R2+1, respectively.

In the access-register mode, access registers 1, R1, R2, and R3 specifythe address spaces containing the parameter block, first operand, secondoperand, and circular history buffer, respectively. When DFTCC-CMPR withan in-line history buffer is specified in the access-register mode,access register R2 specifies the address space containing the in-linehistory. When DFTCC-XPND with an in-line history buffer is specified inthe access-register mode, access register R1 specifies the address spacecontaining the in-line history.

Further details regarding the various functions are described below:

Function Code 0: DFLTCC-QAF (Query Available Functions)

The DFLTCC-QAF (query available functions) function provides a mechanismto indicate the availability of the installed functions and installedparameter block formats. One example format of a parameter block for theDFLTCC-QAF function is described with reference to FIG. 3J. In oneexample, a parameter block 340 for the DFLTCC-QAF function (e.g.,function code 0) includes an installed functions vector 342 and aninstalled parameter block formats vector 346. In one particular example,these vectors are stored to bytes 0-15 and bytes 24-25, respectively, ofthe parameter block. Each of the vectors is further described below.

As an example, bits 0-127 of installed functions vector 342 correspondto function codes 0-127, respectively, of the DEFLATE Conversion Callinstruction. When a bit is, e.g., one, the corresponding function isinstalled; otherwise, the function is not installed.

Further, in one example, bits 0-15 of installed parameter block formatsvector 346 correspond to parameter block formats 0-15, respectively forthe DFLTCC-GDHT, DFLTCC-CMPR and DFLTCC-XPND functions. When a bit is,e.g., one, the corresponding parameter block format is installed;otherwise, the parameter block format is not installed. In one example,zeros are stored to reserved bytes 16-23 and 26-31 of the parameterblock.

Although certain fields are described with respect to parameter block340, additional, fewer and/or other fields may be included in otherembodiments.

The contents of general registers R1, R2, R3, R1+1, and R2+1 are ignoredby the DFLTCC-QAF function, in one embodiment.

A PER (program event recording) storage alteration event is recognized,when applicable, for the parameter block. A PER zero address detectionevent is recognized, when applicable, for the parameter block.

In one example, condition code 0 is set when execution of the DFLTCC-QAFfunction completes; condition codes 1, 2, and 3 are not applicable tothe query function, in one example.

Function Code 1: DFLTCC-GDHT (Generate Dynamic-Huffman Table)

When the DFLTCC-GDHT function is specified, the second operand is used,for instance, as a source to generate a compressed representation of adynamic-Huffman table (DHT), as specified by the DEFLATE standard.

In one example, the DFLTCC-GDHT function uses a parameter block, anexample of which is described with reference to FIG. 3K. In the exampleparameter block described herein, specific locations within theparameter block for specific fields and specific sizes of the fields areindicated (e.g., specific bytes and/or bits). However, other locationsand/or sizes may be provided for one or more of the fields. Further,although the setting of a bit to a particular value e.g., one or zero,is specified, this is only an example. The bit may be set to a differentvalue, such as the opposite value or to another value, in otherexamples. Many variations are possible.

Additionally, in one example, the parameter block includes one or morepreserved fields and one or more reserved fields. Preserved fields arenot modified by the DFLTCC-GDHT function. Preserved fields aredistinguished from reserved fields to enable a program to initialize asingle storage location, use that storage location for the parameterblock of a DFLTCC-GDHT function, and subsequently use the same storagelocation for the parameter block of a DFLTCC-CMPR function. Reservedfields are to contain zeros; otherwise, the program may not operatecompatibly in the future. When an operation ends, reserved fields may bestored as zeros or may remain unchanged.

Yet further, some of the fields are used by other functions (e.g.,DFLTCC-CMPR or DFLTCC-XPND), and thus, aspects relating to thosefunctions may also be described with the description of those fields.

In one example, a parameter block 360 for the DFLTCC-GDHT functionincludes the following fields:

Parameter Block Version Number (PBVN) 362: Bytes 0-1 of the parameterblock specify the version and size of the parameter block. Bits 0-11 ofthe PBVN are reserved and should contain zeros; otherwise, the programmay not operate compatibly in the future. Bits 12-15 of the PBVN containan unsigned binary integer specifying the format of the parameter block.The DFLTCC-QAF function provides a mechanism to indicate the parameterblock formats available. When the format of the parameter blockspecified is not supported by the model, a general operand dataexception is recognized. The PBVN is specified by the program and is notmodified during execution of the instruction.

Model Version Number (MVN) 363: Byte 2 of the parameter block is anunsigned binary integer identifying the model which executed theinstruction. The program is not required to initialize the MVN. The MVNis updated during execution of the instruction. The value stored in theMVN is model-dependent.

Dynamic-Huffman Table (DHT) Generation Control (DHTGC) 364: Bit 2 ofbyte 17 of the parameter block applies to generating a dynamic-Huffmantable (DHT). The DHT specifies Huffman codes for symbols representingliteral bytes, duplicate string lengths, end-of-block (EOB) symbol, andduplicate string pointer distances. The value of a Huffman code for aparticular symbol is a function of the count of occurrences for theentity, which the symbol represents, in the uncompressed form of thedata. When the count for a symbol is zero, there is no Huffman code inthe DHT for the symbol. The DHTGC specifies counts equal to zero will betreated as follows, in one example:

DHTGC Meaning 0 Treat counts of literal bytes, duplicate string lengths,and pointer distances equal to zero as equal to one (generate auniversal DHT). 1 Treat counts of duplicate string lengths and pointerdistances equal to zero as equal to one.

A DHT which specifies a Huffman code for every possible value of literalbytes, an EOB symbol, duplicate string lengths, and duplicate stringpointer distances is called a universal DHT. A DHT which does notspecify Huffman codes for values of literal bytes, duplicate stringlengths, or duplicate string pointer distances which do not occur in theuncompressed form of the data is called a non-universal DHT.

For all values of the DHTGC, the resulting DHT specifies Huffman codesfor all possible duplicate string lengths and pointer distances, asdefined by the DEFLATE standard. Therefore, the HLIT (Huffman literal)and HDIST (Huffman distances) sub-elements of the resulting compressedform of the DHT, described further below, each contain the value of, forinstance, 29.

The DHTGC is an input to the operation when the DFLTCC-GDHT function isspecified. The DHTGC does not apply to the operation when theDFLTCC-CMPR or DFLTCC-XPND function is specified. The DHTGC is notmodified, in one embodiment, during execution of the instruction.

Operation Ending Supplemental Code (OESC) 365: Byte 19 of the parameterblock is an unsigned binary integer providing additional information onthe condition being reported to the program. Since this field is used bymultiple functions, some of the conditions refer to fields of aparameter block used by other functions (e.g., the parameter block ofFIG. 3L used by the DFLTCC-CMPR and DFLTCC-XPND functions). When thecondition being reported is a general operand data exception, theoperation is considered suppressed, although the OESC field of theparameter block is updated, in which case it is defined as follows, inone example:

OESC (hex) Meaning 00 No additional information is provided. 01 Theformat of the parameter block, as specified by parameter block versionnumber 362, is not supported by the model. 02 The DFLTCC-CMPR orDFLTCC-XPND function is specified, a history length field 385 (FIG. 3L)is greater than, e.g., 32,768, and a new task field 374 (FIG. 3L) iszero. 11 A compressed data block with BTYPE (Block Type) equal to 11binary is encountered. 12 A compressed data block with BTYPE equal to 00binary and NLEN not equal to the one's complement of LEN (length) isencountered. 21 CDHTL field 366 (FIG. 3L) applies and is, e.g., lessthan 42 or greater than 2283. 22 The HLIT sub-element of a compressedDHT used during the operation is, e.g., greater than 29 (invalid DHT).23 The HDIST sub-element of a compressed DHT used during the operationis, e.g., greater than 29 (invalid DHT). 24 A compressed DHT used duringthe operation specifies a code which is in the sequence of codesspecifying the bit lengths for the possible code lengths (e.g., 19)defined for a compressed DHT and is less than the length required by theHuffman algorithm to specify a functional Huffman tree (invalid DHT). 26A compressed DHT used during the operation specifies code length 16(copy previous code length) as the first code length for the set ofelements consisting of literal bytes, an EOB symbol, and duplicatestring lengths (invalid DHT). 27 A compressed DHT used during theoperation specifies a code which is in the sequence of codes specifyingcode lengths for literal bytes, and the code does not match any of thecodes determined to represent the set of referenced code lengths, asspecified earlier in the compressed DHT (invalid DHT). 28 A compressedDHT used during the operation specifies a code which assigns code length0 (CL0) to the EOB symbol. In this case, the corresponding DHT does notspecify a Huffman code to represent an EOB symbol (invalid DHT). 29 Acompressed DHT used during the operation specifies a code which is inthe sequence of codes specifying code lengths for duplicate stringlengths and pointer distances, and the code does not match any of thecodes determined to represent the set of referenced code lengths, asspecified earlier in the compressed DHT (invalid DHT). 2A A compressedDHT used during the operation specifies a number of code lengths whichis greater than the number of Huffman codes in the DHT, as specified bythe sum of the values in the HLIT field, the HDIST field, and, e.g.,258. This is possible with an improper uses of code lengths 16, 17, and18, as examples (invalid DHT). 2B A compressed DHT used during theoperation specifies a code length for the set of literal bytes, EOBsymbol, and duplicate string lengths, which is less than the lengthrequired by the Huffman algorithm to specify a functional Huffman tree(invalid DHT). 2D A compressed DHT used during the operation specifies acode length for the set of duplicate string pointer distances, which isless than the length required by the Huffman algorithm to specify afunctional Huffman tree (invalid DHT). 2F CDHTL field 366 (FIG. 3L)applies and does not equal the length of the compressed DHT in CDHTfield 367 (FIG. 3L) used during the operation. 31 A compressed DHT usedduring the operation does not specify a Huffman code corresponding to aliteral byte or a duplicate string length processed during the operation(deficient non-universal DHT), or the DFLTCC-XPND function is specifiedand a compressed data symbol, which is encountered in a compressed datablock with BTYPE equal 01 binary, specifies an invalid code for aduplicate string length (11000110 or 11000111 binary). 32 A compressedDHT used during the operation does not specify a Huffman codecorresponding to a duplicate string pointer distance processed duringthe operation (deficient non-universal DHT), or the DFLTCC-XPND functionis specified and a compressed data symbol, which is encountered in acompressed data block with BTYPE equal 01 binary, specifies an invalidcode for a duplicate string pointer distance (11110 or 11111 binary). 40A compressed data symbol is encountered which is a duplicate stringpointer and specifies a distance greater than the length of historyavailable at the point of processing the symbol.

When the operation ends without reporting a general operand dataexception, zeros are stored to the OESC field.

Support for supplemental codes other than zero is model-dependent. Whenmultiple conditions exist, it is model-dependent which code, if any, isreported in the OESC field.

Compressed Dynamic-Huffman Table Length (CDHTL) 366: Twelve bits,starting with bit 4 of byte 56 through bit 7 of byte 57, of theparameter block contain an unsigned binary integer which specifies thelength, as a bit count, of the compressed format of the DHT in the CDHTfield of the parameter block (e.g., CDHT 367).

The CDHTL is an output from the operation when the DFLTCC-GDHT functionis specified.

The CDHTL is an input to the operation when the DFLTCC-CMPR function isspecified and the Huffman table type (e.g., HTT 376 of FIG. 3L) is one.When the CDHTL does not specify an appropriate length for the CDHT, ageneral operand data exception is recognized. The CDHTL is not modifiedwhen the DFLTCC-CMPR function is specified.

When the DFLTCC-XPND function is specified and the operation ends afterdecoding only a portion of a block with BTYPE 10 binary, the length ofthe compressed representation of the DHT in the block is stored to thisfield. When the DFLTCC-XPND function is specified and the operation endsat a block boundary or after decoding only a portion of a block withBTYPE 00 or 01 binary, zeros are stored to this field. When anuncompressing operation is resumed within a block with BTYPE 10 binary(that is when CF (continuation flag 373 of FIG. 3L) equals one and IFS(incomplete function status 383) equals C or D hex, described below),this field is an input to the operation.

Compressed Dynamic-Huffman Table (CDHT) 367: Bytes 64-351 of theparameter block contain a compressed format of a dynamic-Huffman table(DHT).

The DHT specifies Huffman codes (bit sequences) to represent two sets ofelements. The elements for one set include literal bytes, an EOB symbol,and duplicate string lengths. The elements for the other set includeduplicate string pointer distances. The compressed representation of theDHT defines a set of code lengths and specifies a code length (CL) foreach element of each set. The Huffman code for an element expected to bereferenced during an operation is derived from the CL specified for thatelement and the number of elements in the same set with the samespecified CL. Specifically, the compressed representation of the DHTincludes the following, as an example:

-   -   An HUT field to specify the number of Huffman codes representing        literal bytes, an EOB symbol and duplicate string lengths.    -   An HDIST field to specify the number of Huffman codes        representing duplicate string pointer distances.    -   An HCLEN (Huffman code lengths) field to specify the number of        Huffman codes representing code lengths.    -   A sequence of codes specifying a bit length for each of the, for        instance, 19 code lengths defined for the compressed DHT.    -   A sequence of codes specifying a code length for each of the        elements of the set consisting of literal bytes, an EOB symbol,        and duplicate string lengths.    -   A sequence of codes specifying a code length for each of the        elements of the set consisting of duplicate string pointer        distances.

Further details of a compressed representation of a DHT are describedbelow with reference to the description of a compressed data block withblock type 10 binary.

In one example, the compressed representation of the DHT is leftjustified in the CDHT field. That is, the rightmost bit of byte 64contains the least-significant bit of the HLIT sub-element of thecompressed representation of the DHT.

The compressed representation of a DHT is an output from the operationwhen the DFLTCC-GDHT function is specified.

The compressed representation of a DHT is an input to the operation whenthe DFLTCC-CMPR function is specified and HTT, described below, is one.The CDHT field is not modified by the DFLTCC-CMPR function.

When the DFLTCC-XPND function is specified and the operation ends afterdecoding only a portion of a block with BTYPE 10 binary, the compressedrepresentation of the DHT in the block is stored to this field. When theDFLTCC-XPND function is specified and the operation ends at a blockboundary or after decoding only a portion of a block with BTYPE 00 or 01binary, zeros are stored to this field. When an uncompressing operationis resumed within a block with BTYPE 10 binary (that is when CF equalsone and IFS equals C or D hex), this field is an input to the operation.

When the CDHT is modified, bits of the field not used to represent thecompressed representation of the DHT are stored as zeros.

Although various fields are described above with respect to parameterblock 360, additional, fewer and/or other fields may be included inother embodiments.

Aspects of DHT generation are specified by the program to the machineusing dynamic-Huffman table generation control (DHTGC) field 364 of theparameter block. It is intended that the source contains uncompresseddata and subsequent to completing the operation, the generated result isspecified with the DFLTCC-CMPR function to compress the same source.

In one embodiment, there is no history to reference from prioroperations while processing the current operation.

When the contents of general register R2+1 specify a length greaterthan, e.g., 32 K-bytes, the following applies, in one example:

-   -   Only the first 32 K-bytes of the second operand are used to        generate the DHT.    -   Access exceptions are not recognized for locations beyond the        first 32 K-bytes of the second operand.

When the contents of general register R2+1 specify a length equal tozero, a specification exception is recognized, and the second operand isnot accessed.

The resulting compressed DHT includes a Huffman code representing anend-of-block (EOB) symbol.

A compressed format of the generated DHT is stored to compresseddynamic-Huffman Table (CDHT) field 367 of the parameter block. Thelength of the compressed format of the generated DHT is stored to CDHTLfield 366 of the parameter block.

The operation includes storing a model identification to a model versionnumber field 363 of the parameter block.

When the operation ends without recognizing a general operand dataexception, zeros are stored to operation ending supplemental code (OESC)field 365 of the parameter block.

Condition code 0 is set when execution of the DFLTCC-GDHT functioncompletes; condition codes 1, 2 and 3 are not applicable to theDFLTCC-GDHT function.

General registers R2 and R2+1 are not modified by the operation.

The contents of general registers R1, R1+1 and R3 are ignored when theDFLTCC-GDHT function is specified.

A PER zero address detection event is recognized, when applicable, forthe second operand location and for the parameter block.

Function Code 2: DFLTCC-CMPR (Compress)

When the DFLTCC-CMPR function is specified, a compressing operation isperformed. The operation includes encoding data from the second operandlocation into compressed data symbols, which are stored to the firstoperand location.

In one example, the DFLTCC-CMPR function uses a parameter block, anexample of which is described with reference to FIG. 3L. Some of thefields have been described above with respect to parameter block 360,and therefore, are listed below with the same reference number and notfurther described in detail.

In one example, parameter block 370 includes:

Parameter Block Version Number (PBVN) 362.

Model Version Number (MVN) 363.

Continuation Flag (CF) 373: Bit 63 of the parameter block, when one,indicates the operation is partially complete and the contents of thecontinuation state buffer (e.g., in continuation state buffer field 392)may be used to resume the operation. The program is to initialize thecontinuation flag (CF) to zero and not modify CF in the event theinstruction is to be re-executed for the purpose of resuming theoperation; otherwise results are unpredictable.

New Task (NT) 374: Bit 0 of byte 16 of the parameter block, when one,indicates the operation applies to the beginning of a compressed dataset. Therefore, no history and no check value from a prior operationapplies to the current operation. When NT is one at the beginning of theoperation, and the operation ends after partial completion, zero isstored to the NT field. When NT is zero, history and a check value froma prior operation apply to the current operation.

Check Value Type (CVT) 375: Bit 2 of byte 16 of the parameter blockspecifies the type of check value contained in the check value field ofthe parameter block (e.g., field 387). When CVT is zero, the check valuetype is, e.g., a 32-bit cyclic-redundancy-check (CRC-32). When CVT isone, the check value type is, e.g., a 32-bit Adler checksum (Adler-32).The CVT bit is not modified during execution of the instruction.

Huffman Table Type (HTT) 376: Bit 4 of byte 16 of the parameter block,when zero, specifies a table containing fixed-Huffman codes (FHT), asdefined by the DEFLATE standard, is used during a compression operation.When the HTT is one, a table containing dynamic-Huffman codes (DHT), asspecified in the CDHT field of the parameter block, is used during acompression operation. The HTT does not apply to decompressingoperations. The HTT bit is not modified during execution of theinstruction.

Block Continuation Flag (BCF) 377: Bit 5 of byte 16 of the parameterblock applies when the DFLTCC-CMPR function is specified. When zero, a3-bit block header, and when applicable, the compressed format of adynamic-Huffman table, as specified in the CDHT field of the parameterblock (e.g., field 367), is stored to the first operand location priorto storing any compressed data elements. When one, neither a blockheader nor a compressed format of a DHT is stored to the first operandlocation. When NT is one, BCF is treated as equal to zero. The BCF bitis not modified during execution of the instruction.

Block Closing Control (BCC) 378: Bit 6 of byte 16 of the parameter blockapplies when the DFLTCC-CMPR function is specified. When one, subsequentto storing all compressed data symbols, an end-of block (EOB) symbol isstored to the first operand location. When the HTT specifies using anFHT, Huffman code 0000000 binary (which corresponds to the intermediateinteger representation of 256 in the table specifying codes for literalbytes, an EOB symbol, and duplicate string lengths), as an example, isused for the EOB symbol. When the HTT specifies using a DHT, the Huffmancode for the EOB symbol is specified in the DHT. When the BCC bit iszero, an EOB symbol is not stored to the first operand location. The BCCbit is not modified during execution of the instruction.

Block Header Final (BHF) 379: Bit 7 of byte 16 of the parameter blockapplies when the DFLTCC-CMPR function is specified and either BCF 377 iszero or NT 374 is one; otherwise the BHF does not apply. When applicableand one, the first bit of the block header (BFINAL) is set to one beforestoring the block header to the first operand location. When applicableand zero, the first bit of the block header (BFINAL) is set to zerobefore storing the block header to the first operand location. The BHFbit is not modified during execution of the instruction.

DHT Generation Control (DHTGC) 364: The DHTGC does not apply to theoperation when the DFLTCC-CMPR function is specified. The DHTGC is notmodified during execution of the instruction.

Sub-Byte Boundary (SBB) 381: Bits 5-7 of byte 18 of the parameter blockcontain an unsigned binary integer specifying the boundary betweenprocessed and unprocessed bits within a byte of the compressed datastream. The byte of the stream referenced is the last byte referenced,meaning the rightmost byte, when an operation ends, and is the firstbyte to be referenced, meaning the leftmost byte, when an operationbegins or resumes. When the DFLTCC-CMPR function is specified, the SBBapplies to the byte designated by the first operand address. When theDFLTCC-XPND function is specified, the SBB applies to the bytedesignated by the second operand address. The SBB specifies the numberof rightmost bits that have been processed. The SBB is an input to theoperation and an output of the operation.

One example of a compressed data stream when SBB has a value of 011binary is depicted in FIG. 4. The data that has been processed after theend of the operation is depicted at 400; and the data to be processedbefore the start of the operation is depicted at 402.

Further, FIGS. 5A-5C provide examples which demonstrate how the SBBapplies to the DFLTCC-CMPR function. For instance, one example of howSBB applies before and after executing the DFLTCC-CMPR function isdepicted in FIG. 5A. Other examples are depicted in FIGS. 5B-5C. When NT374 is one, SBB 381 is treated as equal to 000 binary.

Returning to FIG. 3L, additional fields of parameter block 370 aredescribed:

Operation Ending Supplemental Code (OESC) 365.

Incomplete Function Status (IFS) 383: Bits 4-7 of byte 21 of theparameter block contain status information when certain operations end.When a decompressing operation ends, the IFS conveys information aboutthe second operand as follows, in on example:

IFS (binary) Meaning 0000 The operation ended after decoding the lastelement of a block with BFINAL equal to one. 1000 The operation endedafter decoding an element, other than the last element, of a block withBTYPE equal 00 binary and BFINAL equal to zero. 1001 The operation endedafter decoding an element, other than the last element, of a block withBTYPE equal 00 binary and BFINAL equal to one.

In one embodiment, an uncompressing operation may end with IFS equal0000 binary and not satisfy normal completion. In such cases, theoperation ends with condition code 1 or 3 set.

When a compressing operation ends, the IFS field is undefined, but maybe modified.

The IFS is not an input to the operation.

Incomplete Function Length (IFL) 384: Bytes 22-23 of the parameter blockcontain length information when certain operations end. For adecompressing operation, the IFL applies to the second operand. When adecompressing operation ends after decoding some, but not all of a blockwith BTYPE equal 00 binary, the IFL contains an unsigned binary integerspecifying the number of bytes of the block in the second operand, whichhave not yet been processed. Bytes 22-23 contain the IFL in, forinstance, big-endian byte order unlike the LEN field of a block withBTYPE equal 00 binary, which is in, for instance, little-endian byteorder.

When a decompressing operation ends after decoding a complete block withBTYPE equal 00 binary and BFINAL equal to one, zeros are stored to theIFL field. When a decompressing operation ends after decoding some, butnot all of a block with a non-zero BTYPE, or ends at a block boundary,the IFL field is undefined, but may be modified.

When a compressing operation ends, the IFL field is undefined, but maybe modified.

The IFL is not an input to the operation.

History Length (HL) 385: Bytes 44-45 of the parameter block contain anunsigned binary integer specifying the number of bytes of history in thehistory buffer which can be referenced during an operation. The HLapplies to in-line and circular history buffers. When new task (NT)equals one, no history applies to the beginning of the operation and thehistory length is treated as zero as an input to the operation.

A general operand data exception is recognized when the history lengthis greater than, e.g., 32,768 and NT equals zero.

The history length is modified during compressing and decompressingoperations. When the sum of the original HL and the number ofuncompressed data bytes processed during the operation is less than, orequal to, e.g., 32,768, the updated HL is equal to the sum of theoriginal HL and the number of uncompressed data bytes processed duringthe operation; otherwise the updated HL is equal to the value of 32,768.

History Offset (HO) 386: Fifteen bits, starting with bit 1 of byte 46,through bit 7 of byte 47, of the parameter block, contain an unsignedbinary integer specifying an offset in the third operand when thehistory buffer type is circular. The sum of the contents of R3 and thehistory offset designates the location of the first byte of historywithin the circular history buffer, which is the least recentlyprocessed byte of uncompressed data in the buffer. When the historybuffer type is circular, history offset is an input to the operation andis updated at the end of the operation. When the sum of the original HLand the number of uncompressed data bytes processed during the operationis less than, or equal to, e.g., 32,768, the updated HO is equal to theoriginal HO; otherwise, the updated HO is equal to the sum of theoriginal HO, the original HL, and the number of uncompressed data bytesprocessed during the operation, modulo 32,768.

When the history buffer type is in-line, the HO field of the parameterblock is undefined, but may be modified.

Check Value 387: Bytes 48-51 of the parameter block contain a checkvalue. As part of the operation, a check value is generated. The checkvalue applies to the uncompressed data operand. That is, the check valueapplies to the second operand for the DFLTCC-CMPR function and appliesto the first operand for the DFLTCC-XPND function. When CVT bit 375 iszero, a, e.g., 32-bit cyclic-redundancy-check check value (CRC-32) isgenerated. When the CVT bit is one, a, e.g., 32-bit Adler checksum checkvalue (Adler-32) is generated.

The inputs to generating a check value are, for instance, a 4-byte baseand the uncompressed data processed during the operation. The base inputprovides the means to compute a single and consistent check value for aset of compressed data blocks, regardless of the number of times theDFLTCC instruction is executed to process the complete set of compresseddata blocks. When the NT bit is zero, the original value in the checkvalue field is used for the base input in generating a check value.

When an Adler-32 check value is generated, the following apply, in oneexample:

-   -   When the NT bit is one, a value of one is used for the 4-byte        base input.    -   The sums defined in the Adler-32 check value generation are        modulo 65,521.    -   The result is stored to the check value field in big-endian byte        order. That is, the most significant byte of the check value is        located in byte 48 and the least significant byte of the check        value is located in byte 51.

When a CRC-32 check value is generated, the following apply, in oneembodiment:

-   -   When the NT bit is one, a value of zero is used for the 4-byte        base input.    -   The polynomial used as the divisor in generating a CRC-32 check        value is x32+x26+x23+x22+x16+x12+x11+x10+x8+x7+x5+x4+x2+x1+x0,        which is represented as 104C11DB7 hex. In this representation,        the leftmost bit corresponds to the most significant bit.    -   The first and final stages of generating the check value are        computing the one's complement of the base input and computing        the one's complement of the result, prior to storing the result,        respectively.    -   The result is stored to the check value field in little-endian        byte order. That is, the least significant byte of the check        value is located in byte 48 and the most significant byte of the        check value is located in byte 51.

In one example, the check value is only meaningful to the program whenthe operation ends with condition code 0 set; otherwise, the check valueis only an intermediate result and only meaningful to resume theoperation. When the DFLTCC-CMPR function is specified and the operationends with condition code 1, 2, or 3 set some bytes to the left of thebyte designated by the second operand address may not be included in thecomputation of the resulting check value. When the DFLTCC-XPND functionis specified and the operation ends with condition code 1, 2, or 3 set,some result bytes not yet stored to the right of the byte designated bythe first operand address may already be included in the computation ofthe resulting check value.

End-Of-Block Symbol (EOBS) 388: Fifteen bits, starting with bit 0 ofbyte 52, through bit 6 of byte 53, of the parameter block, contain anend-of-block (EOB) symbol. The end-of-block length (EOBL) field 389 ofthe parameter block specifies the length of the EOB symbol in the EOBSfield. The EOB symbol is left justified in the EOBS field. Bits of theEOBS field not occupied by the EOB symbol are stored as zeros. The EOBSfield is an output of the operation when compressing data, regardless ofwhich type of Huffman table applies. The EOBS field is not used as aninput to the operation.

Bit 0 of byte 52 contains the most significant bit of the EOB symbol.When the length of the EOB symbol is 7 bits, bit 6 of byte 52 containsthe least significant bit of the EOB symbol. When the length of the EOBsymbol is 15 bits, bit 6 of byte 53 contains the least significant bitof the EOB symbol.

For blocks using a FHT, the EOB symbol is 0000000 binary, as defined bythe DEFLATE standard. For blocks using a DHT, the EOB symbol is definedby the DHT. The EOB symbol is conveyed in order to provide thecapability for the program to close a block.

The EOBS field is undefined when the DFLTCC-XPND function is specifiedbut may be modified.

End-Of-Block Length (EOBL) 389: Bits 0-3 of byte 54 of the parameterblock contain an unsigned binary integer specifying the length of theend-of-block (EOB) symbol in EOBS field 388 of the parameter block. Thelength specifies the number of bits which the EOB symbol occupies in theEOBS field. The EOBL field is an output of the operation whencompressing data, regardless of which type of Huffman table applies. TheEOBL field is not used as an input to the operation.

The EOBL field is undefined when the DFLTCC-XPND function is specified,but may be modified.

Compressed Dynamic-Huffman Table Length (CDHTL) 366.

Compressed Dynamic-Huffman Table (CDHT) 367: The compressedrepresentation of a DHT is an input to the operation when theDFLTCC-CMPR function is specified and HTT is one. The CDHT field is notmodified by the DFLTCC-CMPR function.

Continuation State Buffer (CSB) 392: When conditions cause a value ofone to be stored in CF field 373, internal state data is stored to bytes384-1535 of the parameter block; otherwise, bytes 384-1535 of theparameter block are undefined and may be modified. The internal statedata stored is model-dependent and may be used subsequently to resumethe operation. It is expected, but not required, for the program toinitialize the continuation state buffer to contain, e.g., all zeros.Subsequent to the instruction ending with a non-zero condition code set,and prior to re-executing the instruction for the purpose of resumingthe operation, the program should not modify the continuation statebuffer; otherwise results are unpredictable.

Although various fields are described above with respect to parameterblock 370, additional, fewer and/or other fields may be included inother embodiments.

One example of the compress operation is described below with respect toCompressing Data.

Normal completion for the DFLTCC-CCMPR function occurs when the entiresecond operand is compressed and stored to the first operand location.When the operation ends due to normal completion, the following occurs,in one example:

-   -   A model-dependent value is stored to model version number (MVN)        field 363 of the parameter block.

Continuation flag (CF) field 373 of the parameter block is set to zero.

-   -   Sub-byte boundary (SBB) field 381 of the parameter block is        updated.

End-of-block length (EOBL) 389 and end-of block symbol (EOBS) 388 fieldsof the parameter block are updated.

-   -   History length (HL) field 385 of the parameter block is updated.    -   The history offset (HO) field 386 of the parameter block is        updated, when applicable.    -   Operation ending supplemental code (OESC) field 365 of the        parameter block is set to zeros.    -   Check value field 387 of the parameter block is updated.    -   The address in general register R1 is incremented by the number        of bytes processed of the first operand that included processing        bit 0, and the length in general register R1+1 is decremented by        the same number. The number of bytes processed of the first        operand that included processing bit 0 is the integer quotient        resulting from an integer division with the dividend being the        sum of the number of output bits processed and the original        value of the SBB, and the divisor being a value of eight.    -   The address in general register R2 is incremented by the number        of source bytes processed, and the length in general register        R2+1 is decremented by the same number.    -   Condition code 0 is set.

The formation and updating of the addresses and lengths are dependent onthe addressing mode.

When normal completion occurs, CSB field 392 of the parameter block isundefined after the operation ends.

When a CPU-determined number of bytes have been processed, the operationends and the following occurs, in one example:

-   -   Continuation flag (CF) bit 373 in the parameter block is set to        one.    -   Continuation state buffer (CSB) field 392 in the parameter block        is updated.    -   Sub-byte boundary (SBB) field 381 of the parameter block is        updated.    -   History length (HL) field 385 of the parameter block is updated.    -   History offset (HO) field 386 of the parameter block is updated,        when applicable.    -   Check value field 387 of the parameter block is updated.    -   A model-dependent value is stored to model version number (MVN)        field 363 of the parameter block.    -   End-of-block length (EOBL) 389 and end-of block symbol (EOBS)        388 fields of the parameter block are updated.    -   Operation ending supplemental code (OESC) field 365 of the        parameter block is set to zeros.    -   The address in general register R1 is incremented by the number        of bytes processed of the first operand that included processing        bit 0, and the length in general register R1+1 is decremented by        the same number. The number of bytes processed of the first        operand that included processing bit 0 is the integer quotient        resulting from an integer division with the dividend being the        sum of the number of output bits processed and the original        value of the SBB, and the divisor being a value of eight.    -   The address in general register R2 is incremented by the number        of source bytes processed, and the length in general register        R2+1 is decremented by the same number.    -   Condition code 3 is set.

The formation and updating of the addresses and lengths are dependent onthe addressing mode.

The CPU-determined number of bytes depends on the model, and may be adifferent number each time the instruction is executed.

Subsequent to the instruction ending with condition code 3 set, it isexpected the program does not modify any input or output specificationfor the instruction and branches back to re-execute the instruction toresume the operation.

In certain situations, despite ending the instruction with conditioncode 3 set, the parameter block and general registers are not updated.These situations may occur when the CPU performs a quiescing operationor CPU retry while executing the DEFLATE Conversion Call instruction. Inthese cases, the CPU-determined number of bytes processed is zero, datamay have been stored to the first operand location, data may have beenstored to the third operand location, when applicable, and correspondingchange bits have been set.

The first operand length is insufficient to complete the operation whenany of the following conditions apply, in one example:

-   -   The first operand length, as specified by the contents of        general register R1+1, is zero at the beginning of the execution        of the instruction.    -   The first operand length becomes equal to zero during execution        of the instruction and normal completion does not occur.

In one example, the first operand length is zero when the content ofgeneral register R1+1 is zero, regardless of the values in the NT andSBB fields of the parameter block.

When the first operand length becomes equal to zero during execution ofthe instruction, the operation ends and the following occurs, in oneembodiment:

-   -   Continuation flag (CF) bit 373 in the parameter block is set to        one.    -   Continuation state buffer (CSB) field 392 in the parameter block        is updated.    -   Sub-byte boundary (SBB) field 381 of the parameter block is        updated.    -   History length (HL) field 385 of the parameter block is updated.    -   History offset (HO) field 386 of the parameter block is updated,        when applicable.    -   Check value field 387 of the parameter block is updated.    -   A model-dependent value is stored to model version number (MVN)        field 363 of the parameter block.    -   End-of-block length (EOBL) 389 and end-of block symbol (EOBS)        388 fields of the parameter block are updated.    -   Operation ending supplemental code (OESC) field 365 of the        parameter block is set to zeros.    -   The address in general register R1 is incremented by the number        of bytes processed of the first operand that included processing        bit 0, and the length in general register R1+1 is decremented by        the same number. The number of bytes processed of the first        operand that included processing bit 0 is the integer quotient        resulting from an integer division with the dividend being the        sum of the number of output bits processed and the original        value of the SBB, and the divisor being a value of eight.    -   The address in general register R2 is incremented by the number        of source bytes processed, and the length in general register        R2+1 is decremented by the same number.    -   Condition code 1 is set.

The formation and updating of the addresses and lengths are dependent onthe addressing mode.

When the first operand length is zero at the beginning of the executionof the instruction, the operation ends and the following occurs, in oneembodiment:

-   -   Condition code 1 is set.

Subsequent to the instruction ending with condition code 1 set, it isexpected that the program modifies the first operand length, firstoperand address, or both and re-executes the instruction to resume theoperation.

A PER storage alteration event is recognized, when applicable, for thefollowing:

-   -   Stores to the parameter block, as described below.    -   Stores to the first operand location.    -   Stores to the third operand location, which occur, e.g., when        the history buffer type (HBT) is one (circular).

When the entire parameter block overlaps the PER storage areadesignation, a PER storage alteration event is recognized, whenapplicable, for the parameter block. When only a portion of theparameter block overlaps the PER storage area designation, it ismodel-dependent which of the following occurs:

-   -   A PER storage alteration event is recognized when applicable,        for the parameter block.    -   A PER storage alteration event is recognized, when applicable,        for the portion of the parameter block that is stored.

A PER zero-address-detection event is recognized when applicable, forthe parameter block, first operand location, second operand location,and third operand location when the HBT is one (circular).

Condition code 2 is not applicable to the DFLTC-CCMPR function.

When the instruction ends with condition code 1 or 3 set, input datareferenced from the second operand location may be completely, or onlypartially, processed. When input data is only partially processed,results in the first operand location, first operand address, firstoperand length, and SBB field of the parameter block do not represent astate consistent with the updated second operand address and length. Inthese cases, partially processed data and internal-state information maybe placed in the CSB field of the parameter block. The amount ofpartially processed data depends on conditions existing at the time theoperation ends and the model. Although some data may only be partiallyprocessed, results stored to the left of the location designated by theupdated first operand address are complete and will not be modified whenthe operation resumes. Furthermore, it is expected that the programsubsequently re-executes the instruction to resume the operation, atwhich time the contents of the CSB field are referenced prior toresuming the operation. When the instruction ends with condition code 0set, all data is completely processed and all results associated withinput and output data represent a consistent state.

Subsequent to the instruction ending with a non-zero condition code set,and prior to re-executing the instruction for the purpose of resumingthe operation, the program should not modify any fields of the parameterblock; otherwise results are unpredictable.

Function Code 4: DFLTCC-XPND (Expand)

When the DFLTCC-XPND function is specified, an uncompressing operationis performed. The operation includes decoding compressed data symbolsfrom the second operand location into uncompressed data, which is storedto the first operand location.

In one example, the DFLTCC-XPND function uses a parameter block, anexample of which is described above with respect to FIGS. 3K-3L.

One example of the DFLTCC-XPND operation is described below with respectto Uncompressing Data.

Normal completion occurs when all elements of the final block of thedata set in the second operand are decoded and all uncompressed data isstored to the first operand location. The last block of the data set isidentified when the BFINAL bit of the block header is one. When theoperation ends due to normal completion, the following occurs, in oneembodiment:

-   -   A model-dependent value is stored to model version number (MVN)        field 363 of the parameter block.    -   Continuation flag (CF) field 373 of the parameter block is set        to zero.    -   Sub-byte boundary (SBB) field 381 of the parameter block is        updated.    -   History length (HL) field 385 of the parameter block is updated.    -   History offset (HO) field 386 of the parameter block is updated,        when applicable.    -   Compressed dynamic-Huffman table (CDHT) 367 and compressed        dynamic-Huffman table length (CDHTL) fields 366 of the parameter        block are set to zeros.    -   Operation ending supplemental code (OESC) field 365 of the        parameter block is set to zeros.    -   Check value field 387 of the parameter block is updated.    -   The address in general register R1 is incremented by the number        of bytes stored at the first operand location, and the length in        general register R1+1 is decremented by the same number.    -   The address in general register R2 is incremented by the number        of bytes processed of the second operand that included        processing bit 0, and the length in general register R2+1 is        decremented by the same number. The number of bytes processed of        the second operand that included processing bit 0 is the integer        quotient resulting from an integer division with the dividend        being the sum of the number of input bits processed and the        original value of the SBB, and the divisor being a value of        eight.

Condition code 0 is set.

The formation and updating of the addresses and lengths are dependent onthe addressing mode.

When normal completion occurs, CSB field 392 of the parameter block isundefined after the operation ends.

When a CPU-determined number of bytes have been processed, the operationends and the following occurs, in one embodiment:

-   -   Continuation flag (CF) bit 373 in the parameter block is set to        one.    -   Continuation state buffer (CSB) field 392 in the parameter block        is updated.    -   Sub-byte boundary (SBB) field 381 of the parameter block is        updated.    -   Compressed dynamic-Huffman table (CDHT) 367 and compressed        dynamic-Huffman table length (CDHTL) 366 fields of the parameter        block are updated. When partial completion occurs while        processing a block with BTYPE value of 10 binary, the bytes of        the CDHT field not required to represent the table are stored as        zeros. When partial completion occurs while processing a block        with BTYPE value of 00 or 01 binary, zeros are stored to the        CDHT and CDHTL fields.    -   History length (HL) field 385 of the parameter block is updated.    -   History offset (HO) field 386 of the parameter block is updated,        when applicable.    -   Check value field 387 of the parameter block is updated.    -   A model-dependent value is stored to model version number (MVN)        field 363 of the parameter block.    -   Operation ending supplemental code (OESC) field 365 of the        parameter block is set to zeros.    -   Incomplete function status (IFS) field 383 of the parameter        block is updated.    -   Incomplete function length (IFL) field 384 of the parameter        block is updated, when applicable.    -   The address in general register R1 is incremented by the number        of bytes stored at the first operand location, and the length in        general register R1+1 is decremented by the same number.    -   The address in general register R2 is incremented by the number        of bytes processed of the second operand that included        processing bit 0, and the length in general register R2+1 is        decremented by the same number. The number of bytes processed of        the second operand that included processing bit 0 is the integer        quotient resulting from an integer division with the dividend        being the sum of the number of input bits processed and the        original value of the SBB, and the divisor being a value of        eight.    -   Condition code 3 is set.

The formation and updating of the addresses and lengths are dependent onthe addressing mode.

The CPU-determined number of bytes depends on the model, and may be adifferent number each time the instruction is executed.

Subsequent to the instruction ending with condition code 3 set, it isexpected the program does not modify any input or output specificationfor the instruction and branches back to re-execute the instruction toresume the operation.

In certain situations, despite ending the instruction with conditioncode 3 set, the parameter block and general registers are not updated.These situations may occur when the CPU performs a quiescing operationor CPU retry while executing the DEFLATE Conversion Call instruction. Inthese cases, the CPU-determined number of bytes processed is zero, datamay have been stored to the first operand location, data may have beenstored to the third operand location, when applicable, and correspondingchange bits have been set.

The second operand length is insufficient to complete the operation whenthe following applies, for instance:

-   -   The last element of a compressed data block with BFINAL equal to        one has not been decoded during the operation, and the number of        bits in the second operand, as designated by the second operand        length and SBB, is less than the number of bits of the next        element to decode and all results from decoding data from the        second operand location have been placed at the first operand        location.

When the second operand length is insufficient to complete theoperation, the operation has been partially completed, the operationends, and the following occurs, in one embodiment:

-   -   Continuation flag (CF) bit 373 in the parameter block is set to        one.    -   Continuation state buffer (CSB) field 392 in the parameter block        is updated.    -   Sub-byte boundary (SBB) field 381 of the parameter block is        updated.    -   Compressed dynamic-Huffman table (CDHT) 367 and compressed        dynamic-Huffman-table length (CDHTL) fields 366 of the parameter        block are updated. When partial completion occurs while        processing a block with BTYPE value of 10 binary, the bytes of        the CDHT field not required to represent the table are stored as        zeros. When partial completion occurs while processing a block        with BTYPE value of 00 or 01 binary, zeros are stored to the        CDHT and CDHTL fields.    -   History length (HL) field 385 of the parameter block is updated.    -   History offset (HO) field 386 of the parameter block is updated,        when applicable.    -   Check value field 387 of the parameter block is updated.    -   A model-dependent value is stored to the model version number        (MVN) field 363 of the parameter block.    -   Operation ending supplemental code (OESC) field 365 of the        parameter block is set to zeros.    -   Incomplete function status (IFS) field 383 of the parameter        block is updated.    -   Incomplete function length (IFL) field 384 of the parameter        block is updated, when applicable.    -   The address in general register R1 is incremented by the number        of bytes stored at the first operand location, and the length in        general register R1+1 is decremented by the same number.    -   The address in general register R2 is incremented by the number        of bytes processed of the second operand that included        processing bit 0, and the length in general register R2+1 is        decremented by the same number. The number of bytes processed of        the second operand that included processing bit 0 is the integer        quotient resulting from an integer division with the dividend        being the sum of the number of input bits processed and the        original value of the SBB, and the divisor being a value of        eight.    -   Condition code 2 is set.

The formation and updating of the addresses and lengths are dependent onthe addressing mode.

Subsequent to the instruction ending with condition code 2 set, it isexpected that the program modifies the second operand length, secondoperand address, or both and re-executes the instruction to resume theoperation.

The first operand length is insufficient to complete the operation whenthe following applies, for instance:

-   -   Results from decoding data from the second operand location        cannot be placed at the first operand location due to the first        operand length being equal to zero.

When the first operand length is insufficient to complete the operation,the operation has been partially completed, the operation ends, and thefollowing occurs, in one embodiment:

-   -   Continuation flag (CF) bit 373 in the parameter block is set to        one.    -   Continuation state buffer (CSB) field 392 in the parameter block        is updated.    -   Sub-byte boundary (SBB) field 381 of the parameter block is        updated.    -   The compressed dynamic-Huffman table (CDHT) 367 and compressed        dynamic-Huffman-table length (CDHTL) fields 366 of the parameter        block are updated. When partial completion occurs while        processing a block with BTYPE value of 10 binary, the bytes of        the CDHT field not required to represent the table are stored as        zeros. When partial completion occurs while processing a block        with BTYPE value of 00 or 01 binary, zeros are stored to the        CDHT and CDHTL fields.    -   History length (HL) field 385 of the parameter block is updated.    -   History offset (HO) field 386 of the parameter block is updated,        when applicable.    -   Check value field 387 of the parameter block is updated.    -   A model-dependent value is stored to model version number (MVN)        field 363 of the parameter block.    -   Operation ending supplemental code (OESC) field 365 of the        parameter block is set to zeros.    -   Incomplete function status (IFS) field 383 of the parameter        block is updated.    -   Incomplete function length (IFL) field 384 of the parameter        block is updated, when applicable.    -   The address in general register R1 is incremented by the number        of bytes stored at the first operand location, and the length in        general register R1+1 is decremented by the same number.    -   The address in general register R2 is incremented by the number        of bytes processed of the second operand that included        processing bit 0, and the length in general register R2+1 is        decremented by the same number. The number of bytes processed of        the second operand that included processing bit 0 is the integer        quotient resulting from an integer division with the dividend        being the sum of the number of input bits processed and the        original value of the SBB, and the divisor being a value of        eight.    -   Condition code 1 is set.

The formation and updating of the addresses and lengths are dependent onthe addressing mode.

Subsequent to the instruction ending with condition code 1 set, it isexpected that the program modifies the first operand length, firstoperand address, or both and re-executes the instruction to resume theoperation.

A PER storage-alteration event is recognized, when applicable, for thefollowing:

Stores to the parameter block, as described herein.

Stores to the first operand location.

Stores to the third operand location, which occur, e.g., when thehistory buffer type (HBT) is one (circular).

In one example, when the entire parameter block overlaps the PER storagearea designation, a PER storage alteration event is recognized, whenapplicable, for the parameter block. When only a portion of theparameter block overlaps the PER storage area designation, it ismodel-dependent which of the following occurs, in one embodiment:

-   -   A PER storage alteration event is recognized when applicable,        for the parameter block.    -   A PER storage alteration event is recognized, when applicable,        for the portion of the parameter block that is stored.

A PER zero-address-detection event is recognized when applicable, forthe parameter block, first operand location, second operand location,and third operand location when the HBT is one (circular).

When the instruction ends with condition code 1, 2, or 3 set, input datareferenced from the second operand location may be completely, or onlypartially, processed. When input data is only partially processed,results in the first operand location, first operand address, firstoperand length, SBB field of the parameter block, check value field ofthe parameter block, HL field of the parameter block, IFS field of theparameter block, and when applicable, the third operand location and HOfield of the parameter block, do not represent a state consistent withthe updated second operand address and length. In these cases, partiallyprocessed data and internal state information may be placed in the CSBfield of the parameter block. The amount of partially processed datadepends on conditions existing at the time the operation ends and themodel. Although some data may only be partially processed, resultsstored to the left of the location designated by the updated firstoperand address are complete and will not be modified when the operationresumes. Furthermore, it is expected that the program subsequentlyre-executes the instruction to resume the operation, at which time thecontents of the CSB field are referenced prior to resuming theoperation. When the operation ends with condition code 0 set, all datais completely processed and all results associated with input and outputdata represent a consistent state.

Subsequent to the instruction ending with a non-zero condition code set,and prior to re-executing the instruction for the purpose of resumingthe operation, the program should not modify any fields of the parameterblock; otherwise results are unpredictable.

Compressed Data Blocks

In one example, the bytes of a compressed data block in storage areprocessed from, e.g., left to right. Compressed data blocks may, or maynot, start or end on byte boundaries. A compressed data block is, forinstance, a bit stream. Elements of the block are loaded into storageone bit at a time. The bit stream is loaded, e.g., from right to leftwithin each byte of storage and in byte order from, e.g., left to right.When the element is a Huffman code, the bits are stored in order from,e.g., most significant bit to least significant bit of the element. Whenthe element is not a Huffman code, the bits are stored in order from,e.g., least significant bit to most significant bit of the element.

FIG. 6 illustrates an example of a block 600 with block type 00 binary,which contains no compressed data symbols. The following applies to thisexample, in one embodiment:

-   -   Compressed data block 600 consists of a bit stream 602 which        begins with bit 4 of byte 0, identified as b0, and ends with bit        0 of byte 7, identified as b60.    -   The first element encountered in the bit stream is BFINAL (block        header final bit) in bit 4 of byte 0.    -   The second element encountered in the bit stream is BTYPE (block        type) in bits 2-3 of byte 0. In this example, the BTYPE is 00        binary.    -   Bits to the left of the BTYPE and to the right of a byte        boundary are ignored when the BTYPE is 00 binary, which is bits        0-1 of byte 0 in this example.    -   The third element encountered in the bit stream is the least        significant byte (LSB) of the LEN field, which is followed by        the most significant byte (MSB) of the LEN field. The LEN field        specifies the number of bytes in the block with literal data.        Literal data is, e.g., uncompressed data. The bytes with literal        data follow the NLEN field in the bit stream. NLEN is the one's        complement of LEN. In one example, bytes 1-2 contain the LEN        field in little-endian byte order.    -   The elements encountered in the bit stream following the LEN        field are the least significant byte of the NLEN field, followed        by the most significant byte of the NLEN field, respectively.        Bytes 3-4 contain the NLEN field in little-endian byte order.        The NLEN field is the one's complement of the LEN field.    -   Elements encountered in the bit stream following the NLEN field        are uncompressed data, identified as literal bytes. Bytes 5-7        contain uncompressed data, which is unchanged from the source        data used to generate this block.    -   None of the elements contained in this block are Huffman codes.        Every element in this block is stored to the bit stream order in        order from least significant bit to most significant bit of the        element, as defined by the DEFLATE standard. Since the LEN,        NLEN, and literal elements are each an integral number of bytes        aligned on byte boundaries, these elements may be processed as        units of bytes, and not necessarily as units of bits.

FIG. 7 illustrates an example of a block 700 with block type 01 binary,which contains compressed data symbols generated using a fixed-Huffmantable (FHT). The following applies to this example, in one embodiment:

-   -   Compressed data block 700 consists of a bit stream 702 which        begins with bit 4 of byte 0, identified as b0, and ends with bit        3 of byte 11, identified as b89.    -   The first element encountered in the bit stream is BFINAL in bit        4 of byte 0.    -   The second element encountered in the bit stream is BTYPE in        bits 2-3 of byte 0. In this example, the BTYPE is 01 binary.    -   The fixed-Huffman table (FHT) is not a component of the block.    -   The third element encountered in the bit stream is the first        compressed data symbol, which begins in bit 1 of byte 0. A        compressed data symbol consists of the following sub-elements        which are encountered in the bit stream in the order in which        they are listed, in one example:        -   1. A Huffman code of variable length. The most significant            bits of the code designate the length of the code. The code            is encountered in the bit stream starting with the most            significant bit of the code and ending with the least            significant bit of the code. When the code represents a            literal value or the end-of-block symbol, the code is the            only sub-element of the compressed data symbol. When the            code represents a length of a pointer to the history buffer,            the code is followed by subsequent sub-elements of the            compressed data symbol.        -   2. When applicable, as specified by the DEFLATE standard,            extra length bits may follow the Huffman code representing a            pointer length. Extra length bits are encountered in the bit            stream starting with the least significant bit and ending            with the most significant bit of the extra length bits.        -   3. The next sub-element encountered in the bit stream is a            5-bit distance code of a pointer to the history buffer. The            distance code is encountered in the bit stream starting            with, e.g., the most significant bit of the code and ending            with the least significant bit of the distance code.        -   4. When applicable, as specified by the DEFLATE standard,            extra distance bits may follow the distance code. Extra            distance bits are encountered in the bit stream starting            with the least significant bit and ending with the most            significant bit of the extra distance bits.    -   Bits 0-1 of byte 0, all bits of bytes 1 through 9 and bits 2-7        of byte 10 contain bits of compressed data symbols, as an        example.    -   The last element encountered in the bit stream is a compressed        data symbol containing a single sub-element, which is the        Huffman code representing the end-of-block (EOB) symbol. The EOB        symbol for a block with BTYPE 01 binary is 0000000 binary. In        this example, bit 1 of byte 10 contains the most significant bit        of the EOB symbol and bit 3 of byte 11 contains the least        significant bit of the EOB symbol.    -   Bit 3 of byte 11 contains the last bit of the bit stream, which        is the last bit of the compressed data block.

FIG. 8 illustrates an example of a block 800 with block type 10 binary,which contains compressed data symbols generated using a dynamic-Huffmantable (DHT). The following applies to this example, in one embodiment:

-   -   Compressed data block 800 consists of a bit stream 802 which        begins with bit 4 of byte 0, identified as b0, and ends with bit        3 of byte 11, identified as b89.    -   The first element encountered in the bit stream is BFINAL in bit        4 of byte 0.    -   The second element encountered in the bit stream is BTYPE in        bits 2-3 of byte 0. In this example, the BTYPE is 10 binary.    -   The third element encountered in the bit stream is the        compressed representation of the dynamic-Huffman table (DHT),        which begins in bit 1 of byte 0. The compressed representation        of the DHT consists of the following sub-elements, which are        encountered in the bit stream in the order which they are        listed, in one example:        -   1. HLIT: The sum of the 5-bit HLIT sub-element and 257            specifies the number of Huffman codes representing literal            bytes, an EOB symbol, and duplicate string lengths. Valid            values of HLIT range from, e.g., 0 to 29. HLIT bits are            encountered in the bit stream starting with the least            significant bit and ending with the most significant bit of            the HLIT sub-element. In this example, bit 1 of byte 0,            identified as b3 is the least significant bit of the HLIT            sub-element.        -   2. HDIST: The sum of the 5-bit HDIST sub-element and 1            specifies the number of Huffman codes representing duplicate            string pointer distances. Valid values of HDIST range from,            e.g., 0 to 29. HDIST bits are encountered in the bit stream            starting with the least significant bit and ending with the            most significant bit of the HDIST sub-element.        -   3. HCLEN: The sum of the 4-bit HCLEN sub-element and 4            specifies the number of Huffman codes representing code            lengths. Valid values of HCLEN range from, e.g., 0 to 15.            HCLEN bits are encountered in the bit stream starting with            the least significant bit and ending with the most            significant bit of the HCLEN sub-element.        -   4. A sequence of codes specifying a bit length for each of            the code lengths defined for the compressed DHT. The number            of codes is equal to the sum of HCLEN and 4. Each code is 3            bits.        -   5. A sequence of codes specifying a code length for each of            the elements of the set consisting of literal bytes, an EOB            symbol, and duplicate string lengths. The number of code            lengths specified is equal to the sum of HLIT and 257.

When the last code length (CL) for the set of literal bytes, an EOBsymbol, and duplicate string lengths is 16, 17, or 18, and the extrabits following the CL specify repeating the CL for more elements thanare defined for the set, the code length also applies to the set ofduplicate string pointer distances. The sequence of codes specifyingcode lengths for the set of literal bytes, an EOB symbol and duplicatestring lengths, followed by the sequence of codes specifying codelengths for duplicate string pointer distances is a contiguous sequencefor both sets.

-   -   6. A sequence of codes specifying a code length for each of the        elements of the set consisting of duplicate string pointer        distances. The number of code lengths specified is equal to the        sum of HDIST and 1.    -   The fourth element encountered in the bit stream is the first        compressed data symbol. A compressed data symbol consists of the        following sub-elements, which are encountered in the bit stream        in the order which they are listed, in one embodiment:        -   1. A Huffman code of variable length. The most significant            bits of the code designate the length of the code. The code            is encountered in the bit stream starting with the most            significant bit of the code and ending with the least            significant bit of the code. When the code represents a            literal value or the end-of-block symbol, the code is the            only sub-element of the compressed data symbol. When the            code represents a length of a pointer to the history buffer,            the code is followed by subsequent sub-elements of the            compressed data symbol.        -   2. When applicable, as specified by the DEFLATE standard,            extra length bits may follow the Huffman code representing a            pointer length. Extra length bits are encountered in the bit            stream starting with, e.g., the least significant bit and            ending with the most significant bit of the extra length            bits.        -   3. The next sub-element encountered in the bit stream is a            5-bit distance code of a pointer to the history buffer. The            distance code is encountered in the bit stream starting            with, e.g., the most significant bit of the code and ending            with the least significant bit of the distance code.        -   4. When applicable, as specified by the DEFLATE standard,            extra distance bits may follow the distance code. Extra            distance bits are encountered in the bit stream starting            with, e.g., the least significant bit and ending with the            most significant bit of the extra distance bits.    -   Subsequent bits encountered in the bit stream, up to and        including, e.g., bit 5 of byte 10, contain bits of compressed        data symbols.    -   The last element encountered in the bit stream is a compressed        data symbol containing a single sub-element, which is the        Huffman code representing the end-of-block (EOB) symbol. In this        example, bit 4 of byte 10 contains the most significant bit of        the EOB symbol and bit 3 of byte 11 contains the least        significant bit of the EOB symbol.    -   Bit 3 of byte 11 contains the last bit of the bit stream, which        is the last bit of the compressed data block.

In the above descriptions of the various block types, certain constantvalues are specified, as well as specific bits, bytes, directions, etc.These are only examples. Other constant values, bits, bytes, directions,etc. may be specified in other embodiments.

Processing a Compressed Data Set

Examples of processing a compressed data set to illustrate example usesof the DEFLATE Conversion Call instruction and augment the descriptionsof various fields of the parameter block are provided. The examples donot describe all possible scenarios, requirements, and capabilities, butillustrate various of the scenarios, requirements and/or capabilities.The examples and descriptions apply, for instance, to a compressed dataset in storage, an example of which is illustrated in FIG. 9. As shown,a compressed data set 900 includes a plurality of compressed data blocks902, and a beginning of data set 900 is indicated by a compressed dataset begin address (CDSBA) 904.

For the examples described herein, it is intended for a programprocessing the compressed data set to consider the following, in oneembodiment:

-   -   A single parameter block may be defined and referenced by        multiple usages of the DEFLATE Conversion Call instruction to        process the entire compressed data set. Check value 387 and        check value type 375 fields of the parameter block shall apply        to the compressed data blocks (e.g., all blocks) in the        compressed data set. Sub-byte boundary field 381 of the        parameter block shall apply to transitions between individual        blocks. History length 385 and history offset 386 may apply to        multiple blocks. The remaining fields of the parameter block        only apply, in one example, to the individual compressed data        block being processed by a specific execution of a DEFLATE        Conversion Call instruction.    -   An individual check value applies, e.g., to all of the        uncompressed data represented by the compressed data set.    -   There is no history for the first compressed data symbol in        block 1 to reference. Subsequent symbols in block 1 may        reference history corresponding to previously encountered        symbols in block 1. Symbols in block 2 may reference history        corresponding to previously encountered symbols in blocks 2 and        1. Symbols in block 3 may reference history corresponding to        previously encountered symbols in blocks 3, 2, and 1.

FIG. 10 lists one example of a portion of a sample program 1000 used tocompress data in compressed data set 900 described in FIG. 9. Further,FIG. 11 lists the values for certain fields of the parameter block usedduring execution of the DFLTCC instruction located at the instructionaddress labeled IABLK1 (1002) in FIG. 10. For instance, FIG. 11 depictsvarious parameter block fields 1100; values for those fields at thestart of the compress operation 1102; values for those fields at the endof the operation when condition code 1, 2 or 3 is set 1104; and valuesfor those fields at the end of the operation when condition code 0 isset 1106.

Similarly, FIG. 12 lists the values for certain fields of the parameterblock used during execution of the DFLTCC instruction located at theinstruction address labeled IABLK2 (1004) of FIG. 10. These figuresdemonstrate some of the details associated with using the DEFLATEConversion Call instruction multiple times to process an entirecompressed data set.

Moreover, referring to FIG. 13, one example of a portion of a sampleprogram 1300 used to decompress data from the compressed data set ofFIG. 9 is depicted.

Compressing Data

The process of compressing data includes generating one or morecompressed data blocks. The compress function of the DEFLATE ConversionCall instruction is used to construct a portion of an individual block.The portion may be the entire block. This function generates portions ofa block with block type (BTYPE) 01 or 10 binary, and not 00 binary. Whenthe new task bit (NT) of the parameter block is one, the first block ofcompressed data is generated and there is no history to reference frompreviously performed compressing operations.

In one example, an individual block contains the following elements inthe order which they are listed:

-   -   1. Final block indication (BFINAL).    -   2. Block type (BTYPE).    -   3. Compressed format of a dynamic-Huffman table, when        applicable.    -   4. Compressed data symbols.    -   5. End-of-block (EOB) symbol.

The compression operation generates the elements specified in the orderdefined for a block. The elements may begin or end between byteboundaries in storage. The sub-byte boundary (SBB) applies to storing ofthe first element to the first operand location. A compressed data blockis a bit stream. Components of the block are loaded into storage one bitat a time. As an example, the bit stream is loaded from right to leftwithin each byte of storage and in byte order from left to right.

When the SBB is non-zero, the reference to the first byte at the firstoperand location is an update reference.

Uncompressed data from the second operand location is compressed andstored as compressed data symbols to the first operand location.

When the first operand length is zero at the beginning of the executionof the instruction, the first operand is not accessed, and the firstoperand address and first operand length in general registers R1 andR1+1, respectively, are not changed. This applies when the value of CFfield 373 (FIG. 3L) is zero or one at the beginning of execution of theinstruction.

When the second operand length is zero at the beginning of execution ofthe instruction, the second operand is not accessed, and the secondoperand address and second operand length in general registers R2 andR2+1, respectively, are not changed. The second operand length is zeroat the beginning of execution of the instruction for the following case,as an example:

-   -   The instruction is being re-executed to resume the operation (CF        field 373 of the parameter block is one at the beginning of        execution of the instruction) and completing the operation can        be performed with references to CSB field 392 of the parameter        block, and without references to the second operand.

In one embodiment, the program is not to use the DEFLATE Conversion Callinstruction to perform the following operations:

-   -   Generate an empty compressed data block. An empty compressed        data block consists of, e.g., a block header, a compressed        format of a DHT when applicable, and an EOB symbol.    -   Close an open compressed data block. That is, only store an EOB        symbol to the end of the compressed data block.

The compression algorithm includes searching an updated history ofrecently compressed data for a string of bytes which matches datacurrently being compressed from the second operand location. Before thecompression operation begins or resumes, the following applies, in oneembodiment:

-   -   When new task (NT) 374 is one, there is no initial history        available to reference.    -   When NT is zero, and bit 56 of general register 0 (HBT) is zero        (in-line), the initial history available to reference is located        to the left of, and adjacent to, the leftmost byte of the second        operand, and the length of the initial history is specified by        history length (HL) field 385 of the parameter block.    -   When NT is zero, and bit 56 of general register 0 (HBT) is one        (circular), the initial history available to reference is        located in the third operand location, as specified by history        offset (HO) 386 and history length (HL) 385 fields of the        parameter block.

During the compression operation, fetch-type references to the entirehistory may be made, regardless of which bytes of history are used toperform the operation. Furthermore, when the history buffer type iscircular, fetch-type references to the entire 32 K-byte history buffermay be made, regardless of which bytes of history are used to performthe operation.

During the compression operation, history is updated. Subsequent toencoding one or more bytes of source data into a compressed data symbolwithout encountering a general operand data exception condition, thesource bytes are concatenated to the end of the history. The mostrecently processed bytes of source data, up to a maximum of 32 K-bytes,constitute the updated history available to reference while processingsubsequent bytes of source data.

When the compression operation ends, the following applies, in oneexample, to the resulting history available to subsequently resume theoperation, or begin another operation:

-   -   When the HBT is in-line, storage updates to the second operand        location are not required when the history is updated. The        updated second operand address and updated HL specify the        updated location and updated length of the resulting history.    -   When the HBT is circular, storage updates to the third operand        location are performed when the history is updated. The third        operand address, updated HO, and updated HL specify the updated        location and updated length of the resulting history.

As examples, FIGS. 14A-14C illustrate the location of an in-line historybuffer with respect to the second operand before and after multipleexecutions of a DEFLATE Conversion Call instruction with the DFLTCC-CMPRfunction specified, as well as in-line history specified (e.g., bit310=0), when each execution ends with partial completion. For instance,FIG. 14A depicts in-line history before DFLTCC-CMPR execution number 1;FIG. 14B depicts in-line history before DFLTCC-CMPR execution number 2and after execution number 1; and FIG. 14C depicts in-line history afterDFLTCC-CMPR execution number 2. The explanation provided in FIG. 14Calso applies to FIGS. 14A and 14B.

When the HBT (history buffer type) specified by bit 56 of generalregister 0 is circular (e.g., bit 310=1), the history is maintained in,for instance, a 32 K-byte buffer located at the third operand location.The location of the first byte of history within the buffer (HB) isdesignated by, e.g., the sum of the contents of general register R3 andhistory offset (HO) 386 (FIG. 3L). The first byte of history is theleast recently processed byte of uncompressed data in the buffer. Thelocation of the last byte of history within the buffer (HE) isdesignated by the following equation, as an example:

HE=R3+modulo32K(HO+HL−1)

The last byte of history is the most recently processed byte ofuncompressed data in the buffer. When the sum of history offset (HO) 386(FIG. 3L) and history length (HL) 385 exceeds the size of the thirdoperand (e.g., 32 K-bytes), the history wraps from the end of the thirdoperand to the beginning of the third operand.

As examples, FIGS. 15A-15E illustrate the location of the history withina circular history buffer before and after multiple executions of aDEFLATE Conversion Call instruction with the DFLTCC-CMPR functionspecified, as well as a circular history buffer specified (bit 310=1),when each execution ends with partial completion. For instance, FIG. 15Adepicts a circular history buffer before DFLTCC execution number 1; FIG.15B depicts a circular buffer before DFLTCC execution number 2 and afterexecution number 1; FIG. 15C depicts a circular buffer before DFLTCCexecution number 3 and after execution number 2; FIG. 15D depicts thecircular buffer before DFLTCC execution number 4 and after executionnumber 3; and FIG. 15E depicts the circular buffer after DFLTCCexecution number 4. The explanation provided in FIG. 15E also applies toFIGS. 15A-15D.

When the HBT is circular and the number of bytes processed from thesecond operand location is less than, e.g., 32,768, the followingapplies, in one example:

-   -   Stores are made to a range of bytes in the third operand        location. The range of bytes includes and starts with the        location designated by, for instance:

R3+modulo32K(HOO+HLO), where

HOO: The history offset before the instruction executes.

HLO: The history length before the instruction executes.

The range of bytes includes and ends with the location designated by,e.g.:

R3+modulo32K(HOO+HLO+BP−1), where

BP: The number of bytes processed from the second operand locationduring execution of the instruction.

Stores made to the range of bytes just described are subject tostore-type access exceptions, PER storage alteration events, and settingchange bits, as an example.

-   -   Stores which do not modify the contents of storage locations and        are not necessary, may be made to bytes in the third operand        location which are not included in the range just described.        Stores to such locations are also subject to store type access        exceptions, PER storage alteration events, and setting change        bits.

When the HBT is circular and the number of bytes processed from thesecond operand location is more than, or equal to, e.g., 32,768, storesare made to all bytes of the third operand location and subject to storetype access exceptions, PER storage alteration events, and settingchange bits.

When the block continuation flag (BCF) 377 is zero, a 3 bit blockheader, including BFINAL followed by BTYPE, is stored to the firstoperand location. The BFINAL bit of the block header is set equal to theblock header final bit (BHF) 379 of the parameter block. When theHuffman table type (HTT) 376 is zero, the BTYPE field of the blockheader is set to, e.g., 01 binary and when the HTT is one, the BTYPEfield of the block header is set to, e.g., 10 binary. When a blockheader is stored, the BFINAL bit is stored to the bit specified by theSBB in the first byte of the first operand. Subsequently, the BTYPE isstored to the first operand location. When the BCF is one, a blockheader is not stored.

When the Huffman table type (HTT) is one, the compressed format of thedynamic-Huffman table (DHT) 367 specified in the parameter block isexamined for general operand data exception conditions. When a generaloperand data exception condition exists for the specified compressedformat of the DHT, the compressed DHT is referred to as invalid and isnot to be used to compress data. Example definitions of general operanddata exception conditions are described further below. When thecompressed format of the DHT specifies a bit length for a code length,or a code length for a literal byte, the EOB symbol, a duplicate stringlength, or a duplicate string pointer distance, which is greater thanthe length required by the Huffman algorithm to specify a proper andfunctional Huffman tree, the compressed DHT is still used to derive afunctional DHT and compress data. When the block continuation flag (BCF)is zero and the HTT is one, the compressed format of the DHT, asspecified in CDHT field 367 of the parameter block is stored to thefirst operand location.

During the compression operation, source data from the second operandlocation is encoded into compressed data symbols. As part of theencoding, source data is compared to the history. When no match isfound, the intermediate representation of the source data is literalbytes, which is the same as the source data. When a match is found, theintermediate representation of the source data is a pointer to alocation within the history which contains a duplicate copy of thesource data. A pointer consists of a length and a distance. The lengthis the number of source data bytes which match a string in the history.The distance is the number of bytes from the end of the history to thebeginning of the string which matches the source data. Two Huffman codetrees from the Huffman table are used, in one example, to encode theintermediate representation of the source data into compressed datasymbols. When the Huffman table type (HTT) is zero, a fixed-Huffmantable (FHT), as described by the DEFLATE standard, specifies the twoHuffman code trees used for encoding intermediate results. When HTT 376is one, the dynamic-Huffman table (DHT), which is derived from thecompressed representation of the DHT, specified in CDHT field 367 of theparameter block, specifies the two Huffman code trees used for encodingintermediate results. The encoding is performed as described by theDEFLATE standard. When a non-universal DHT is used which does notspecify a Huffman code to be used to encode the intermediaterepresentation of the source data, a general operand data exception isrecognized. The bits of the resulting compressed data symbol arearranged in the order specified by the DEFLATE standard before storingthe result to the first operand location.

In one example, duplicate-string lengths range from 3 to 258 bytes.

Prior to processing further source data, the history is updated, asdescribed herein.

The process is repeated, in one example, until all source bytes havebeen processed.

After the source bytes (e.g., all source bytes) have been processed andthe block closing control (BCC) 378 is one, an end-of-block (EOB) symbolis stored to the first operand location. When a fixed-Huffman table isused, Huffman code 0000000 binary is used for the EOB symbol. When adynamic-Huffman table (DHT) is used, the Huffman code used for the EOBsymbol is specified by the DHT. The bits of the EOB symbol are arrangedin the order specified by the DEFLATE standard before storing the EOBsymbol to the first operand location.

When the last compressed data symbol of the operation (including the EOBsymbol), only occupies a portion of the last byte to store, the bitsthat do not contain a portion of the last symbol are stored as zeros, inone example.

Subsequent to processing the last compressed data symbol, the followingoccurs, in one embodiment:

-   -   A model-dependent value is stored to model version number (MVN)        field 363 of the parameter block.    -   Sub-byte boundary (SBB) field 381 of the parameter block is        updated.    -   End-of-block length (EOBL) 389 and end-of block symbol (EOBS)        388 fields of the parameter block are updated.    -   The address in general register R1 is incremented by the number        of bytes processed of the first operand that included processing        bit 0, and the length in general register R1+1 is decremented by        the same number. The number of bytes processed of the first        operand that included processing bit 0 is the integer quotient        resulting from an integer division with the dividend being the        sum of the number of output bits processed and the original        value of the SBB, and the divisor being a value of eight.    -   The address in general register R2 is incremented by the number        of source bytes processed, and the length in general register        R2+1 is decremented by the same number.

The formation and updating of the addresses and lengths are dependent onthe addressing mode.

Coincident with compressing the source data, the source data is an inputto generating a 32-bit check value, described above. The resulting checkvalue is stored to check value field 387 of the parameter block.

Uncompressing Data

In one embodiment, the expand function of the DEFLATE Conversion Callinstruction is used to decode a compressed data set into uncompresseddata. The compressed data set in the second operand location includesone or more consecutive compressed data blocks. The blocks of the dataset are processed from left to right, in one example, and the bytes of ablock are processed, e.g., from left to right. The blocks may or may notstart or end on byte boundaries. Each block is decoded independent ofother blocks in the data set. General register R2 specifies the logicaladdress of the leftmost byte of the first block in the data set. Thelast block in the data set is the block encountered during processingwith the BFINAL bit equal to one. In one example, there are three typesof blocks to process. The technique of decoding the contents of a blockis a function of the block type (BTYPE).

When the operation begins (e.g., when continuation flag field 373 of theparameter block is zero), the bit designated by general register R2, newtask (NT) field 374, and sub-byte boundary (SBB) field 381 isinterpreted as the first bit of a compressed data block (the BFINAL bitof a block header).

The expand function includes referencing an updated history of recentlydecoded uncompressed data. Before the uncompressing operation begins orresumes, the following applies, in one embodiment:

-   -   When new task (NT) 374 is one, there is no initial history        available to reference.    -   When NT is zero, and bit 56 of general register 0 (HBT) is zero        (in-line), the initial history available to reference is located        to the left of, and adjacent to, the leftmost byte of the first        operand, and the length of the initial history is specified by        history length (HL) field 385 of the parameter block.    -   When NT is zero, and bit 56 of general register 0 (HBT) is one        (circular), the initial history available to reference is        located in the third operand location, as specified by history        offset (HO) 386 and history length (HL) 385 fields of the        parameter block.

During the operation, fetch-type references to the entire history may bemade, regardless of which bytes of history are used to perform theoperation. Furthermore, when the history buffer type is circular,fetch-type references to the entire history buffer (e.g., 32 K-byte) maybe made, regardless of which bytes of history are used to perform theoperation.

During the uncompressing operation, history is updated. Subsequent todecoding source data without encountering a general operand dataexception condition, the resulting bytes of uncompressed data areconcatenated to the end of the history. The most recently decoded bytesof uncompressed data, up to a maximum of, e.g., 32 K-bytes, constitutethe updated history available to reference while processing subsequentsource data.

When the uncompressing operation ends, the following applies to theresulting history available to subsequently resume the operation, orbegin another operation, in one example:

-   -   When the HBT is in-line, storage updates to the first operand        location also constitute updates to the resulting history. The        updated first operand address and updated HL specify the updated        location and updated length of the resulting history.    -   When the HBT is circular, storage updates to the third operand        location are performed when the history is updated. The third        operand address, updated HO, and updated HL specify the updated        location and updated length of the resulting history.

As examples, FIGS. 16A-16C illustrate examples of the location of anin-line history buffer with respect to the first operand before andafter multiple executions of a DEFLATE Conversion Call instruction withthe DFLTCC-XPND function specified, as well as in-line historyspecified, when each execution ends with partial completion. Historylength (HL) 385 is modified during the operation. For instance, FIG. 16Adepicts one example of the in-line history prior to DFLTCC-XPNDexecution number 1; FIG. 16B depicts an example of the in-line historybefore DFLTCC-XPND execution number 2 and after execution number 1; andFIG. 16C depicts an example of the in-line history after DFLTCC-XPNDexecution number 2. The explanation provided in FIG. 16C also applies toFIGS. 16A-16B.

When the HBT specified by bit 56 of general register 0 is circular, thehistory is maintained in, for instance, a 32 K-byte buffer located atthe third operand location. The location of the first byte of historywithin the buffer (HB) is designated by the sum of the contents ofgeneral register R3 and history offset (HO) 386. The first byte ofhistory is the least recently processed byte of uncompressed data in thebuffer. The location of the last byte of history within the buffer (HE)is designated by, e.g., the following equation:

HE=R3+modulo32K(HO+HL−1).

The last byte of history is the most recently processed byte ofuncompressed data in the buffer. When the sum of the history offset (HO)and history length (HL) exceeds the size of the third operand (e.g., 32K-bytes), the history wraps from the end of the third operand to thebeginning of the third operand. FIGS. 15A-15E, described herein,illustrate examples of the location of the history within a circularhistory buffer before and after multiple executions of a DEFLATEConversion Call instruction with the DFLTCC-XPND function and a circularhistory buffer specified, when each execution ends with partialcompletion.

When the HBT is circular and the number of bytes stored to the firstoperand location is less than, e.g., 32,768, the following applies, inone example:

-   -   Stores are made to a range of bytes in the third operand        location. The range of bytes includes and starts with the        location designated by:

R3+modulo32K(HOO+HLO), where

HOO: The history offset before the instruction executes.

HLO: The history length before the instruction executes.

The range of bytes includes and ends with the location designated by,e.g.,

R3+modulo32K(HOO+HLO+BP−1), where

BP: The number of bytes stored to the first operand location duringexecution of the instruction.

Stores made to the range of bytes just described are subject tostore-type access exceptions, PER storage-alteration events, and settingchange bits.

-   -   Stores which do not modify the contents of storage locations and        are not necessary, may be made to bytes in the third operand        location which are not included in the range just described.        Stores to such locations are also subject to store-type access        exceptions, PER storage-alteration events, and setting change        bits.

When the HBT is circular and the number of bytes stored to the firstoperand location is more than, or equal to, e.g., 32,768, stores aremade to, e.g., all bytes of the third operand location and subject tostore-type access exceptions, PER storage-alteration events, and settingchange bits.

When the BTYPE is 00 binary, the block does not contain compressed data.FIG. 6, described herein, illustrates one example of a block with BTYPEequal 00 binary. The LEN field specifies the number of literal bytes inthe block. The byte order of the LEN field is little-endian. The LENfield may specify zero literal bytes. The literal bytes of the block areplaced at the first operand location. The history is also updated, aspreviously described, with each literal byte of the block.

When the BTYPE is 01 binary, the block contains compressed data symbolsthat were generated using a fixed-Huffman table (FHT). The FHT isdefined by the DEFLATE standard and is not part of the block. FIG. 7, asdescribed herein, illustrates one example of a block with BTYPE equal 01binary. Subsequent to interpreting the block header, compressed datasymbols are decoded in the order in which they appear in the block.Bytes of the block are processed from, e.g., left to right and bitswithin each byte of the block are processed from, e.g., right to left.In one example, each symbol is completely processed prior to processingthe next symbol in the block. Each symbol which is not the end-of-block(EOB) symbol represents a literal value or a pointer to a substringpreviously decoded in the history buffer. A previously decoded substringis also referred to as a duplicate string. In one example, duplicatestring lengths range from 3 to 258 bytes. A pointer consists of codesrepresenting the substring length and the distance from the end of thehistory to the beginning of the substring. When a symbol represents asubstring in the history, the substring is referenced from the historybuffer. The uncompressed data resulting from decoding a symbol is placedat the first operand location.

Prior to processing further source data, the history is updated aspreviously described.

The updated history applies to decoding the next symbol of the block.When the EOB symbol is encountered, processing of the block is complete.

When the BTYPE is 10 binary, the block contains compressed data symbolsthat were generated using a dynamic-Huffman table (DHT). A compressedformat of the DHT used is an element of the compressed data block. FIG.8, described herein, illustrates one example of a block with BTYPE equal10 binary. Subsequent to interpreting the block header, the compressedformat of the DHT provided within the compressed data block is examinedfor general operand data exception conditions. When a general operanddata exception condition exists for the provided compressed format ofthe DHT, the compressed format of the DHT is referred to as invalid andis not to be used to uncompress data. When the compressed format of theDHT specifies a bit length for a code length, or a code length for aliteral byte, the EOB symbol, a duplicate string length, or a duplicatestring pointer distance, which is greater than the length required bythe Huffman algorithm to specify a proper and functional Huffman tree,the compressed DHT is still used to derive a functional DHT and compressdata. Subsequent to examining the compressed format of the DHT,compressed data symbols are decoded in the order in which they appear inthe block. Bytes of the block are processed, e.g., from left to rightand bits within each byte of the block are processed from, e.g., rightto left. Each symbol is completely processed, in one example, prior toprocessing the next symbol in the block. The processing of symbols in ablock with BTYPE 10 binary is the same as previously described forprocessing symbols in a block with BTYPE 01, except the former uses theDHT provided to decode symbols, and the latter uses the FHT to decodesymbols. When a non-universal DHT is provided which does not specify aHuffman code to be used to decode a compressed data symbol, a generaloperand data exception is recognized.

Coincident with uncompressing the second operand, the uncompressed datais an input to generating a check value (e.g., a 32-bit check value).The resulting check value is stored to check value field 387 of theparameter block.

Subsequent to processing the last block of the data set, the followingoccurs, in one embodiment:

-   -   A model-dependent value is stored to model version number (MVN)        field 363 of the parameter block.    -   Sub-byte boundary (SBB) field 381 of the parameter block is        updated.    -   The address in general register R1 is incremented by the number        of bytes stored at the first operand location, and the length in        general register R1+1 is decremented by the same number.    -   The address in general register R2 is incremented by the number        of bytes processed of the second operand that included        processing bit 0, and the length in general register R2+1 is        decremented by the same number. The number of bytes processed of        the second operand that included processing bit 0 is the integer        quotient resulting from an integer division with the dividend        being the sum of the number of input bits processed and the        original value of the SBB, and the divisor being a value of        eight.

The formation and updating of the addresses and lengths are dependent onthe addressing mode.

When the first operand length is zero at the beginning of the executionof the instruction, the first operand is not accessed, and the firstoperand address and first operand length in general registers R1 andR1+1, respectively, are not changed. This applies when the value of CFfield 373 is zero or one at the beginning of the execution of theinstruction.

When the second operand length is zero at the beginning of the executionof the instruction, the second operand is not accessed, and the secondoperand address and second operand length in general registers R2 andR2+1, respectively, are not changed. The second operand length is zeroat the beginning of the execution of the instruction for the followingcase, in one embodiment:

-   -   The instruction is being re-executed (e.g., CF field 373 of the        parameter block is one at the beginning of the execution of the        instruction) and the entire second operand was processed when        the instruction was previously executed.

The uncompressing operation may end without storing any results to thefirst operand location, even though data was processed from the secondoperand location. This occurs when the data processed from the secondoperand location only contains any of the following compressed datablock elements, in an example:

A block header.

The LEN field of a block with block type 00 binary.

The NLEN field of a block with block type 00 binary.

A compressed format of a dynamic-Huffman table.

An end-of-block (EOB) symbol.

The following conditions apply to executing the DEFLATE Conversion Callinstruction, in one or more embodiments:

A general operand data exception is recognized when the DFLTCC-GDHTfunction is specified and the following condition occurs, in oneexample:

-   -   The format of the parameter block, as specified by parameter        block version number 362, is not supported by the model.

A general operand data exception is recognized when the DFLTCC-CMPRfunction is specified and any of the following conditions occur, in oneexample:

-   -   The format of the parameter block, as specified by parameter        block version number 362, is not supported by the model.    -   NT 374 is zero and HL 385 is greater than, e.g., 32,768.    -   HTT 376 is one and CDHTL 366 is less than, e.g., 42 or greater        than, e.g., 2283.    -   HTT 376 is one and CDHTL 366 does not equal the length of the        compressed format of the DHT specified in CDHT field 367.    -   HTT 376 is one and the HUT sub-element of the compressed format        of the DHT is greater than, e.g., 29 (invalid DHT).    -   HTT 376 is one and the HDIST sub-element of the compressed        format of the DHT is greater than, e.g., 29 (invalid DHT).    -   HTT 376 is one and the compressed format of the DHT (contents of        CDHT field 367) specifies a code which is in the sequence of        codes specifying the bit lengths for the, e.g., 19 possible code        lengths defined for a compressed DHT, and is less than the        length required by the Huffman algorithm to specify a functional        Huffman tree (invalid DHT).    -   HTT 376 is one and the compressed format of the DHT (contents of        CDHT field 367) specifies code length, e.g., 16 (copy previous        code length) as the first code length for the set of elements        consisting of literal bytes, an EOB symbol, and duplicate string        lengths (invalid DHT).    -   HTT 376 is one and the compressed format of the DHT (contents of        CDHT field 367) specifies a code which is in the sequence of        codes specifying code lengths for literal bytes, and the code        does not match any of the codes determined to represent the set        of referenced code lengths, as specified earlier in the        compressed DHT (invalid DHT).    -   HTT 376 is one and the compressed format of the DHT (contents of        CDHT field 367) specifies a code which assigns code length 0        (CLO) to the EOB symbol. In this case, the corresponding DHT        does not specify a Huffman code to represent an EOB symbol        (invalid DHT).    -   HTT 376 is one and the compressed format of the DHT (contents of        the CDHT field 367) specifies a code which is in the sequence of        codes specifying code lengths for duplicate string lengths and        pointer distances, and the code does not match any of the codes        determined to represent the set of referenced code lengths, as        specified earlier in the compressed DHT (invalid DHT).    -   HTT 376 is one and the compressed format of the DHT (contents of        the CDHT field 367) specifies a number of code lengths which is        greater than the number of Huffman codes in the DHT, as        specified by the sum of the values in the HUT field, the HDIST        field, and, e.g., 258. This is possible with improper uses of        code lengthsl6, 17, and 18, as examples (invalid DHT).    -   HTT 376 is one and the compressed format of the DHT (contents of        the CDHT field 367) specifies a code length for the set of        literal bytes, EOB symbol, and duplicate string lengths, which        is less than the length required by the Huffman algorithm to        specify a functional Huffman tree (invalid DHT).    -   HTT 376 is one and the compressed format of the DHT (contents of        the CDHT field 367) specifies a code length for the set of        duplicate string pointer distances, which is less than the        length required by the Huffman algorithm to specify a functional        Huffman tree (invalid DHT).    -   The CPU attempts to generate a compressed data symbol to        represent a literal byte in the second operand, and the DHT        derived from the contents of the CDHT field is non-universal and        does not specify a Huffman code corresponding to that literal        byte.    -   The CPU attempts to generate a compressed data symbol to        represent a duplicate string in the second operand, and the DHT        derived from the contents of the CDHT field is non-universal and        does not specify a Huffman code corresponding to that duplicate        string length or pointer distance.

A general operand data exception is recognized when, for instance, theDFLTCC-XPND function is specified and any of the following conditionsoccur, as examples:

-   -   The format of the parameter block, as specified by parameter        block version number 362, is not supported by the model.    -   NT 374 is zero and HL 385 is greater than, e.g., 32,768.    -   A compressed data block with BTYPE equal 11 binary is        encountered.    -   A compressed data block with BTYPE equal 00 binary and NLEN not        equal to the one's complement of LEN is encountered.    -   A compressed format of a DHT (contents of a compressed data        block with BTYPE equal 10 binary) is encountered and the HLIT        sub-element of the compressed DHT is greater than, e.g., 29        (invalid DHT).    -   A compressed format of a DHT (contents of a compressed data        block with BTYPE equal 10 binary) is encountered and the HDIST        sub-element of the compressed DHT is greater than, e.g., 29        (invalid DHT).    -   A compressed format of a DHT (contents of a compressed data        block with BTYPE equal 10 binary) is encountered which specifies        a code which is in the sequence of codes specifying the bit        lengths for, e.g., the 19 possible code lengths defined for a        compressed DHT, and is less than the length required by the        Huffman algorithm to specify a functional Huffman tree (invalid        DHT).    -   A compressed format of a DHT (contents of a compressed data        block with BTYPE equal 10 binary) is encountered which specifies        code length, e.g., 16 (copy previous code length) as the first        code length for the set of elements consisting of literal bytes,        an EOB symbol, and duplicate string lengths (invalid DHT).    -   A compressed format of a DHT (contents of a compressed data        block with BTYPE equal 10 binary) is encountered which specifies        a code which is in the sequence of codes specifying code lengths        for literal bytes, and the code does not match any of the codes        determined to represent the set of referenced code lengths, as        specified earlier in the compressed DHT (invalid DHT).    -   A compressed format of a DHT (contents of a compressed data        block with BTYPE equal 10 binary) is encountered which specifies        a code which assigns code length 0 (CLO) to the EOB symbol. In        this case, the corresponding DHT does not specify a Huffman code        to represent an EOB symbol (invalid DHT).    -   A compressed format of a DHT (contents of a compressed data        block with BTYPE equal 10 binary) is encountered which specifies        a code which is in the sequence of codes specifying code lengths        for duplicate string lengths and pointer distances, and the code        does not match any of the codes determined to represent the set        of referenced code lengths, as specified earlier in the        compressed DHT (invalid DHT).    -   A compressed format of a DHT (contents of a compressed data        block with BTYPE equal 10 binary) is encountered which specifies        a number of code lengths which is greater than the number of        Huffman codes in the DHT, as specified by the sum of the values        in the HUT field, the HDIST field, and, e.g., 258. This is        possible with improper uses of code lengths 16, 17, and 18, as        examples (invalid DHT).    -   A compressed format of a DHT (contents of a compressed data        block with BTYPE equal 10 binary) is encountered which specifies        a code length for the set of literal bytes, EOB symbol, and        duplicate string lengths, which is less than the length required        by the Huffman algorithm to specify a functional Huffman tree        (invalid DHT).    -   A compressed format of a DHT (contents of a compressed data        block with BTYPE equal 10 binary) is encountered which specifies        a code length for the set of duplicate string pointer distances,        which is less than the length required by the Huffman algorithm        to specify a functional Huffman tree (invalid DHT).    -   A compressed data symbol, which is encountered in a compressed        data block with BTYPE equal 10 binary, specifies a Huffman code        which is not defined by the non-universal DHT derived from the        compressed format of the DHT in the same block. In this case,        the number of bits of the second operand which are to be        available to process, for the purpose of recognizing the general        operand data exception, is model-dependent. More specifically, a        model attempting to decode an undefined code may process, e.g.,        15 bits prior to recognizing the exception, even though the        exception could be determined after processing less bits.    -   A compressed data symbol is encountered which is a duplicate        string pointer and specifies a distance greater than the length        of history available at the point of processing the symbol.    -   A compressed data symbol, which is encountered in a compressed        data block with BTYPE equal 01 binary, specifies an invalid code        (e.g., a code of 11000110 or 11000111 binary fora duplicate        string length, ora code of 11110 or 11111 binary for a duplicate        string pointer distance). In this case, the number of bits of        the second operand which are to be available to process, for the        purpose of recognizing the general operand data exception, is        model-dependent. More specifically a model attempting to decode        an invalid code may process, e.g., 8 bits, in the case of a        duplicate string length, or 5 bits, in the case of a duplicate        string pointer distance, prior to recognizing the exception,        even though the exception could be determined after processing        less bits.

When a general operand data exception is recognized, the operation isconsidered suppressed, even though operation ending supplemental code(OESC) 365 and model version number (MVN) fields 363 of the parameterblock are updated to provide additional information associated with theexception.

When a DFLTCC-CMPR or DFLTCC-XPND function is being executed and ageneral operand data exception is due to be recognized for the secondoperand, the result is that either the exception is recognized, or theoperation ends with partial completion and condition code, e.g., 3 isset. If condition code 3 is set, the exception will be recognized whenthe instruction is executed again to continue processing the sameoperands and the exception condition still exists.

Other Conditions include, for instance:

The execution of the instruction is interruptible. When an interruptionoccurs, the addresses in general registers R1 and R2, the lengths ingeneral registers R1+1 and R2+1, and specific fields of the parameterblock are updated, so that the instruction, when reexecuted, resumes atthe point of interruption.

When a DFLTCC-CMPR or DFLTCC-XPND function is being executed and anaccess exception is due to be recognized for the first or secondoperand, the result is that either the exception is recognized, or theoperation ends with partial completion and condition code, e.g., 3 isset. If condition code 3 is set, the exception will be recognized whenthe instruction is executed again to continue processing the sameoperands and the exception condition still exists.

As observed by this CPU, other CPUs, and channel programs, references tothe parameter block, first, second, and third operands may bemultiple-access references, accesses to these storage locations are notnecessarily block concurrent, and the sequence of these accesses orreferences is undefined.

Results are unpredictable if the DFLTCC-CMPR or DFLTCC-XPND function isspecified and any of the following apply, in one embodiment:

-   -   The parameter block overlaps the first or second operand.    -   The first operand overlaps the second operand.    -   The specified history buffer type (HBT) is circular and the        third operand overlaps the first operand, the second operand, or        the parameter block.    -   The specified history buffer type (HBT) is in-line, the        DFLTCC-CMPR function is specified, and the history overlaps the        first operand or the parameter block.    -   The specified history buffer type (HBT) is in-line, the        DFLTCC-XPND function is specified, and the history overlaps the        second operand or the parameter block.

In certain situations, despite ending the execution of the DEFLATEConversion Call instruction with a CPU-determined number of bytesprocessed being zero, data may have been stored to the first operandlocation, data may have been stored to the third operand location, whenapplicable, and corresponding change bits have been set, whenapplicable. In these cases, the contents of the parameter block andgeneral registers have not been modified from original values. Thesesituations may occur when the CPU performs a quiescing operation or aCPU retry while executing the DEFLATE Conversion Call instruction.

The following are example Resulting Condition Codes from executing theDEFLATE Conversion Call instruction:

0 Normal completion

1 The first operand length is insufficient to complete the operation

2 The second operand length is insufficient to complete the operation(DFLTCC-XPND)

3 CPU-determined amount of data processed

Program Exceptions:

-   -   Access (fetch, operand 2, in-line history; fetch and store,        parameter block, operand 1, operand 3)    -   Data with DXC 0, general operand    -   Operation (if the DEFLATE conversion facility is not installed)    -   Specification    -   Transaction constraint

Example priorities of execution for the DEFLATE CONVERSION CALLinstruction are shown below:

1.-6. Exceptions with the same priority as the priority ofprogram-interruption conditions for the general case.

7.A Access exceptions for second instruction halfword.

7.B Operation exception.

7.0 Transaction constraint.

8.A Specification exception due to invalid function code or invalidregister number.

8.B Specification exception due to parameter block not designated on a 4K-byte boundary.

8.C Specification exception due to circular history buffer notdesignated on a 4 K-byte boundary.

9. Access exceptions for an access to the parameter block.

10. General operand data exception when specified format of theparameter block is not supported by the mode.

11. Specification exception due to second operand length equal to zeroand CF equal to zero at the beginning of the execution of theinstruction.

12. Condition code 1 due to first operand length equal to zero at thebeginning of the execution of the instruction and DFLTCC-CMPR isspecified.

13.A General operand data exception due to the history length fieldgreater than 32,768 and the new task field is zero when DFLTCC-CMPR orDFLTCC-XPND is specified.

13.B Access exceptions for an access to the first operand and the firstoperand length is non-zero.

13.C Access exceptions for an access to the second operand and thesecond operand length is non-zero.

13.D Access exceptions for an access to in-line history specified at thebeginning of the execution of the instruction.

13.E Access exceptions for an access to the third operand.

14.A General operand data exception due to conditions other than thoseincluded in items 10 and 13.A above.

14.B Condition codes 1, 2 or 3 due to conditions other than thoseincluded in item 12 above.

15. Condition code 0.

Prior to usage, the compressed format of a DHT is examined for theexistence of general operand data exception conditions. When the lengthof the compressed format of a DHT is not precisely defined due to ageneral operand data exception condition, the interpreted length maydepend on the condition, be model-dependent, and does not exceed, e.g.,286 bytes. As a result, when the DFLTCC-XPND function is specified and acompressed format of a DHT with a general operand data exceptioncondition is encountered in the, e.g., rightmost 286 bytes of the secondoperand, it is model-dependent whether the exception condition (priority14.A) or condition code 2 (priority 14.B) is recognized.

Example programming notes are provided below:

-   -   1. When compressing or uncompressing data, it may be more        efficient overall when the operation is performed with a minimum        number of times the DEFLATE Conversion Call instruction is        executed. In other words, executing DFLTCC with a large operand        may be more efficient than executing DFLTCC with small operands        multiple times.    -   2. For the compressing and uncompressing operations, when        condition code 3 is set, the general registers used by the        instruction and the parameter block have been updated such that        the program can branch back to the instruction to continue the        operation.    -   3. In one embodiment, the DEFLATE Conversion Call instruction        may be completed after performing a CPU-determined sub-portion        of the processing specified by the parameters of the        instruction. When the instruction is completed after performing        only a CPU-determined amount of processing instead of all        specified processing, the instruction sets condition code 3. On        such completion, the instruction address in the PSW (program        status word) designates the next sequential instruction, and the        operand parameters of the instruction have been adjusted so that        the processing of the instruction can be resumed by branching        back to the instruction to execute it again. When the        instruction has performed all specified processing, it sets a        condition code other than 3.    -   4. When the DFLTCC-CMPR function is specified and the operation        ends with a non-zero value in the sub-byte boundary (SBB) field        of the parameter block, the operation included storing to the        byte designated by the resulting first operand address. When the        DFLTCC-XPND function is specified and the operation ends with a        non-zero value in the SBB, the operation included fetching the        byte designated by the resulting second operand address.    -   5. When the operation ends with a non-zero condition code set,        CSB field 392 of the parameter block may contain partially        processed data, and it is expected that the program re-executes        the instruction to resume the operation.    -   6. Subsequent to an operation ending with a non-zero condition        code set, and prior to re-executing the instruction for the        purpose of resuming the operation, the program is not to modify        any fields of the parameter block; otherwise results are        unpredictable.    -   7. When the DFLTCC-GDHT function is specified, the compressed        representation of a DHT generated describes three proper-full        Huffman code trees, according to the Huffman algorithm. That is,        no under-full Huffman code trees are described. An under-full        Huffman code tree is derived from a compressed representation of        a DHT which specifies a code length for an element which is        greater than the length required by the Huffman algorithm to        specify a proper and functional Huffman tree.

When the DFLTCC-CMPR function is specified, HTT is one, and thecompressed representation of the DHT includes a description of anunder-full Huffman code tree, the compressed data results can betransformed to the original uncompressed data by using the DFLTCC-XPNDfunction, but not all decoders, which comply to the DEFLATE standard maybe able to transform the results to the original uncompressed data. Thismay occur, for instance, when the compressed representation of a DHTspecified by the program, for the DFLTCC-CMPR function was not generatedas a result of performing the DFLTCC-GDHT function.

-   -   8. When the DFLTCC-CMPR function ends with condition code 1 set,        the result stored to sub-byte boundary (SBB) field 381 of the        parameter block is 000 binary. Recognizing this scenario may be        relevant to a program allocating output buffers for use with the        DEFLATE Conversion Call instruction.

As described herein, in one aspect, a single instruction (e.g., a singlearchitected machine instruction at the hardware/software interface,e.g., DEFLATE Conversion Call instruction) is provided to performcompress and/or decompress operations using a general-purpose processor.This instruction is, for instance, a hardware instruction defined in anInstruction Set Architecture (ISA). As a result, the complexity of theprogram related to the compressing and/or decompressing operations isreduced. Further, performance of the operations, and thus, theprocessor, is improved.

Advantageously, the DEFLATE Conversion Call instruction is dispatched,by, e.g., a programmer, on a general-purpose processor (e.g., a centralprocessing unit, referred to herein as a processor), rather than aspecial-purpose processor, such as an I/O device, an applicationspecific device connected through an I/O interface, or other types ofspecial-purpose processors. Compared to a software implementation,executing the disclosed instruction requires significantly fewerexecution cycles to perform the same operation. Further, compared todispatching an operation to an I/O device, executing the disclosedinstruction does not require I/O operations by an operating system anddoes not trigger the operating system to perform a task switch whilewaiting for the operation to complete.

Although various fields and registers are described, one or more aspectsof the present invention may use other, additional or fewer fields orregisters, or other sizes of fields and registers, etc. Many variationsare possible. For instance, implied registers may be used instead ofexplicitly specified registers or fields of the instruction and/orexplicitly specified registers or fields may be used instead of impliedregisters or fields. Other variations are also possible.

One embodiment of using the DEFLATE Conversion Call instruction isdescribed with reference to FIG. 17. In one example, a program executingon a processor, such as a general-purpose processor, specifies detailsof an operation to be performed in a parameter block in storage andspecifies the location of the parameter block, STEP 1700. For instance,one or more of the fields of a parameter block (e.g., parameter block340, 360 or 370) are provided or set, depending on the function to beperformed. Further, the program specifies the operation to be performed(e.g., query, generate, compress, expand, etc.), STEP 1702.Additionally, the program specifies or updates the location and amountof input data in storage, STEP 1704, as well as the location and size ofthe result buffer in storage, STEP 1706.

Thereafter, the program executes the DEFLATE Conversion Call (DFLTCC)instruction, STEP 1708. In one example, the instruction is dispatched ona general-purpose processor. As examples, it is processed on thegeneral-purpose processor, or, at least in part, is processed byhardware coupled to the general-purpose processor and accessible absentusing an I/O interface.

Based on the instruction terminating, a determination is made as towhether the condition code resulting from execution is equal to a firstdefined value, e.g., 0, INQUIRY 1710. If the condition code is equal tothe first defined value, then processing of the instruction is complete,STEP 1712. However, if the condition code is not equal to the firstdefined value, then a further determination is made as to whether thecondition code is equal to a second defined value, e.g., 3, INQUIRY1714. If the condition code is equal to the second defined valueindicating there is additional data to be processed, then theinstruction is re-executed, STEP 1708. However, if the condition code isnot equal to the second defined value, then another determination ismade as to whether the condition code is set to a third defined value,e.g., 1, INQUIRY 1716. If the condition code is set to the third definedvalue indicating the first operand length is insufficient, thenprocessing continues with STEP 1706; otherwise, the second operandlength is insufficient for the function and processing continues withSTEP 1704.

As indicated, the DEFLATE Conversion Call instruction may be executedmultiple times to compress or decompress a single data stream.Therefore, in one aspect, the DEFLATE Conversion Call instructionincludes an attribute which provides a mechanism for a program todeclare a buffer (e.g., a 32 K-byte buffer), which is used to accumulatethe history of uncompressed data processed during an operation whichspans multiple executions of the DEFLATE Conversion Call instruction.The buffer is, for instance, a circular history buffer.

In one aspect, the DEFLATE Conversion Call instruction uses an indicator(e.g., a bit) in an implied register (e.g., GR0.56) to indicate use of acircular history buffer. When the circular history buffer is indicatedand the specified function to be performed by the DEFLATE ConversionCall instruction is compressing or uncompressing data, a field of theinstruction (e.g., R3) specifies the location in memory of, e.g., a 32K-byte buffer, which the processor uses to fetch history from at thebeginning of an operation and store history to at the end of anoperation. The length of the history within the circular history bufferis specified by a field of a parameter block associated with the DEFLATEConversion Call instruction (e.g., HL field 385), and the beginning ofthe history within the buffer is specified by an offset included inanother field of the parameter block (e.g., HO field 386).

Further details of using a circular history buffer are described withreference to FIG. 18. In one example, a program executing on aprocessor, such as a general-purpose processor, specifies details of anoperation to be performed in a parameter block in storage and specifiesthe location of the parameter block, STEP 1800. For instance, one ormore of the fields of a parameter block (e.g., parameter block 360 or370) are provided or set, depending on the function to be performed.Further, the program specifies the operation to be performed (e.g.,compress, expand, etc.).

Further, in one example, the program allocates and specifies a locationin memory of a pre-defined sized (e.g., 32 K-byte) circular buffer, STEP1802. Additionally, the program places a portion of an uncompressed datastream into a buffer and specifies the location and the size of thebuffer as an input to the DEFLATE Conversion Call instruction, STEP1804, and specifies or updates the location and size of a result bufferin storage, STEP 1806.

The DEFLATE Conversion Call instruction is then executed, STEP 1808.Based on executing the instruction, the processor fetches history from,e.g., a circular history buffer, as an input to the operation, STEP1820, and performs the specified operation, STEP 1822, as describedherein. Further, the processor modifies the history in the circularhistory buffer as an output of the operation, STEP 1824. A determinationis made as to whether the entire data stream has been processed, INQUIRY1826. If not, then processing continues with STEP 1804. Otherwise,processing is complete.

Use of a circular history buffer provides the following, as examples:

When the size of the input or output buffer, specified for use with anindividual execution of the DEFLATE Conversion Call instruction, isrelatively small (e.g., 512 bytes), a history spanning multiple segmentsof buffered data, up to, e.g., 32 K-bytes, may be used as an input tothe DEFLATE Conversion Call instruction, which processes a small numberof bytes.

When the size of the input or output buffer, specified for use with anindividual execution of the DEFLATE Conversion Call instruction, isrelatively large (e.g., 128 K-bytes), a history of the prior segment ofbuffered data, up to, e.g., 32 K-bytes, may be used as a input to theDEFLATE Conversion Call instruction which is processing the first 32K-bytes of data.

In both cases, more history is available to process data than wouldotherwise be available. As a result, the effectiveness of detectingduplicate strings is improved, resulting in improved overall compressionratios. This facilitates processing within the computing environment andimproves performance.

One or more aspects of the present invention are inextricably tied tocomputer technology and facilitate processing within a computer,improving performance thereof. The use of a single architected machineinstruction to perform compressing and/or decompressing improvesperformance within the computing environment. Thecompressed/decompressed data may be used in many technical fields thatmanage and/or use data, such as in computer processing, medicalprocessing, security, inventory control, etc. By providing optimizationsin compressing/decompressing, these technical fields are improved byreducing execution time.

Further details of one or more embodiments, as it relates to one or moreaspects of the present invention, are described with reference to FIGS.19-22.

A brief description of the technology now follows, after which,particular features used by one or more embodiments of the presentinvention for EADM (extended asynchronous data mover) functionscompatibility indication are described. One embodiment of a computingenvironment to incorporate and/or use one or more aspects of the presentinvention is described with reference to FIG. 19.

FIG. 19 depicts an example computing environment according to one ormore embodiments. As one example, computing environment 1900 includesone or more central processing units 1902 coupled to main memory 1904via one or more buses 1906. One or more of the central processing unitsmay execute an operating system 1908, such as the z/OS® operatingsystem.

Central processing units 1902 and main memory 1904 may be furthercoupled to an I/O hub 1920 via one or more connections 1922 (e.g., busesor other connections). The I/O hub provides connectivity to one or moreI/O adapters 1930, which are further coupled to one or more solid statedevices 1940. The adapters and solid state devices are an implementationof storage class memory (e.g., flash memory). The I/O hub is part of anI/O subsystem 1945 facilitating one or more aspects of an embodiment.

In a further embodiment, as depicted in FIG. 2, a computing environment2000 may include a central processing complex (CPC) 2052, which is basedon the z/Architecture® offered by International Business MachinesCorporation. Central processor complex 2052 includes, for instance, oneor more partitions 2054, a hypervisor 2056, one or more centralprocessors 2058, and one or more components of an input/output subsystem2060. In this example, partitions 2054 are logical partitions (e.g.,LPARs), each of which includes a set of the system's hardware resources,virtualized as a separate system.

Each logical partition 2054 is capable of functioning as a separatesystem. That is, each logical partition can be independently reset,initially loaded with an operating system or other control code, ifdesired, and operate with different programs. An operating system orapplication program running in a logical partition appears to haveaccess to a full and complete system, but in reality, only a portion ofit is available. A combination of hardware and licensed internal code(LIC), referred to as firmware, keeps a program in one logical partitionfrom interfering with a program in a different logical partition. Thisallows several different logical partitions to operate on a single ormultiple physical processors in a time-slice manner. As used herein,firmware includes, e.g., the microcode, millicode and/or macrocode ofthe processor (or entity performing the processing). It includes, forinstance, the hardware-level instructions and/or data structures used inimplementation of higher level machine code. In one embodiment, itincludes, for instance, proprietary code that is typically delivered asmicrocode that includes trusted software or microcode specific to theunderlying hardware and controls operating system access to the systemhardware.

In this example, several of the logical partitions have a residentoperating system (OS) 2070, which may differ for one or more logicalpartitions. In one embodiment, at least one logical partition isexecuting the z/OS® operating system.

Logical partitions 2054 are managed by hypervisor 2056, which isimplemented by firmware running on central processors 2058. Logicalpartitions 2054 and hypervisor 2056 each comprises one or more programsresiding in respective portions of main memory 2059 associated with thecentral processors.

Central processors 2058 are physical processor resources that areallocated to the logical partitions. For instance, a logical partition2054 includes one or more logical processors, each of which representsall or a share of a physical processor resource 2058 allocated to thepartition. The logical processors of a particular partition 2054 may beeither dedicated to the partition, so that the underlying processorresource is reserved for that partition; or shared with anotherpartition, so that the underlying processor resource is potentiallyavailable to another partition.

Input/output subsystem 2060 (of which only a portion is depicted)provides connectivity to storage class memory 2080. In this example, anaddress space is provided for the storage class memory which presentsthe memory as flat, hiding the details of the physical implementationfrom the program. As one example, there is one address space system-widefor the storage class memory, but from the view of a configuration(e.g., LPAR or in another embodiment, a virtualized guest) there is oneaddress space into which storage class memory increments are populatedfor each configuration of the system. The storage class memory addressspace is separate and apart from the main storage address space.

In one particular example of the z/Architecture®, the I/O subsystemincludes a channel subsystem, which, not only directs the flow ofinformation between I/O peripheral control units (and devices) and mainmemory, but also between the storage class memory and main memory.However, the I/O subsystem may be other than a channel subsystem.

In the case of a channel subsystem, subchannels are used to perform EADMoperations. These subchannels are referred to as Asynchronous Data Mover(ADM)-type subchannels and are associated with EADM operations, and notI/O devices, like other I/O-type subchannels. An ADM-type subchanneldoes not contain a device number, nor does it contain channel pathinformation. The number of ADM-type subchannels provided for aconfiguration is model dependent. ADM-type subchannels are addressed bya subsystem identification word (SID).

The ADM-type subchannels are used by the EADM Facility, which is anextension to the channel subsystem. As described herein, the EADMFacility allows a program to request the transfer of blocks of databetween main storage and storage class memory, as well as perform otheroperations, such as clear a block of storage class memory or release ablock of storage class memory, compress/decompress one or more blocks ofmemory, etc. In one embodiment, when the EADM Facility is installed:

-   -   One or more ADM-type subchannels are provided which are used for        EADM operations.    -   EADM operations are designated by a specified EADM-operation        block (AOB). The AOB includes an EADM-request block (ARQB) and        an EADM-response block (ARSB), and designates a list of EADM        move-specification blocks (MSBs). For a move operation, the MSBs        contain information about the blocks of data to be moved, such        as the size of the blocks, the source and destination locations        of the blocks, and the direction of the data movement.    -   A program initiates EADM operations by issuing a Start        Subchannel instruction that designates an ADM-type subchannel        and an EADM operation request block (ORB). In turn, the EADM ORB        designates an AOB. The instruction passes the contents of the        EADM ORB to the designated subchannel.    -   When Start Subchannel is issued to initiate EADM operations, the        channel subsystem asynchronously performs the specified        operation.    -   As observed by the program, storage class memory appears to be        block concurrent at a model dependent minimum block size. This        model dependent value is called the SCM block concurrency size.    -   When EADM operations are complete, an I/O interruption is made        pending to the program for the ADM-type subchannel on which the        operations were initiated.

In addition, the EADM facility (e.g., a second machine architecture) canuse the I/O (second machine) interface to also execute a new instructionwith a subset of functions via the SAP using its own separate commandname, mnemonic and code. Also, the EADM facility itself contains a setof EADM features and each one of these features includes a set of EADMcommands. Each EADM command can use one or more instructions and theirfunctions to complete a task (an operation).

The EADM ORB includes the specification of a subchannel key and theaddress of the AOB to be used. The AOB is designated, for instance, on a4 K-byte boundary and may be up to 4 K-byte in size. If more MSBs areneeded than fit into a 4 K-byte AOB, the AOB may specify an MSB listthat is extended into additional storage areas by using MSBs thatdesignate the address of the next MSB in the list, instead ofdesignating a storage area to be used for data transfer.

The first EADM operation is started by the channel subsystem usinginformation in the designated EADM ORB and ARQB in the designated AOB tofetch an MSB. The MSB includes the information that specifies andcontrols the EADM operation to be processed.

Each EADM operation is represented by one MSB. An MSB may specify, forinstance, a transfer of blocks of data from main storage to storageclass memory; a transfer of blocks of data from storage class memory tomain storage; a clearing of blocks of storage class memory; and thereleasing of blocks of storage class memory.

If the blocks of storage to be transferred are not contiguous in mainstorage, a new MSB may be used or the MSB may use indirect addressing byspecifying a list of EADM indirect data address words (AIDAWs) todesignate the noncontiguous blocks.

Since an MSB specifies the transfer of data in only one direction, a newMSB is to be used when there is a change in the direction of thetransfer.

The conclusion of an EADM operation is normally indicated by thecombined status conditions of channel end and device end. This statuscombination represents the combination of primary and secondary statusindicating that the subchannel is available for another start functionafter the status is cleared.

An EADM operation may be terminated prematurely by a Clear Subchannelinstruction. Execution of the Clear Subchannel instruction terminatesexecution of the AOB at the subchannel, clears the subchannel ofindications of the AOB in execution, and asynchronously performs theclear function.

As described herein, this invention provides a new method to indicatewhich new instructions and/or new functions of a first machine interfacethat are also installed and available at an EADM (e.g., second machine)interface. A new EADM sub-functions field is defined in a response blockof a store EADM information CHSC command and each bit (e.g., flag) inthis EADM sub-functions field represents one or more functions of theone or more instructions that are installed and available in the EADMinterface. Turning now to FIGS. 21-22 for further description of theinvention herein.

FIG. 21 depicts a process flow 2100 in accordance with one or moreembodiments. The process flow 2100 relates to when a computer providesan indication if a set of new instructions and/or new functions at afirst machine interface that are needed by an EADM (e.g., secondmachine) interface are also installed and available at the EADMinterface.

The process flow 2100 begins at block 2130, where an EADM sub-functionsfield in a response block of a store EADM information CHSC command isdefined. FIG. 22 depicts a format of command-response block 2200 forstore EADM information in accordance with one or more embodiments.

The format of command-response block 2200 includes various fields 2210,2220, 2230, 2250, 2250, and 2260. For instance, the command-responseblock 2200 includes EADMF flags field 2210, EADM sub-functions flags(ESFF) field 2220, maximum compression data length field 2230, maximumcompression data-specification block (DSB) count field 2250, reservedfield 2250, and reserved field 2260.

Note that each bit (e.g., each ESFF flag) in the EADM sub-functionsfield 2220 represents one or more functions of one or more instructionsthat are installed and available at the EADM interface. Further, theEADMF Flags 2210 field is defined and it contains a flag to determineEADM-Deflate-Compression-functions validity. For instance, theEADM-Deflate-Compression-functions flag indicates if the CPUDeflate-Compress function (DFLTCC-CMPR) and the CPU Deflate-Decompressfunction (DFLTCC-XPND) of the CPU Deflate-Conversion-Call (DFLTCC)instruction are available in the configuration. TheEADM-Perform-Deflate-Compress-Operation (PDCO) command is installed andavailable only if the required EADM-compression feature is installed andavailable where the software is running, and if the requiredEADM-Deflate-Compression-functions flag is set where the software isrunning. Similarly, the EADM-Perform-Deflate-Decompress-Operation (PDDO)command is installed and available only if the required EADM-compressionfeature is installed and available where the software is running, and ifthe required EADM-Deflate-Compression-functions flag is set where thesoftware is running.

In operation, once the EADM sub-functions field in the response block isdefined, the software can issue the store EADM information CHSC command.The SAP then copies the local copy of the EADM sub-functions field intothe EADM sub-functions field of the response block (e.g., thecommand-response block 2200) of the store EADM information CHSC command.The software next receives the response block (e.g., thecommand-response block 2200) of the store EADM Information CHSC command.

At decision block 2140, a determination is made as to whether an EADMsub-functions flag is set (e.g., whether a flag is set in the ESFF field2220). For example, the SAP creates a local copy of the EADMsub-functions field in the response block of the Store EADM InformationCHSC command. It determines, for each EADM sub-functions flag, if anEADM sub-functions flag should be set based on its own support for theEADM sub-functions flag as well as the availability of one or morefunctions of one or more instructions of the first machine (CPU)interface that are represented by the EADM sub-functions flag. Based onthis determination, the SAP either sets or resets each EADMsub-functions flag of the EADM sub-functions field in its local copy ofthe EADM sub-functions field.

If the EADM sub-functions flag is set, the process flow 2100 proceeds toblock 2150 (as indicated by the YES arrow). That is, the set offunctions of the set of instructions that are represented by that EADMsub-functions flag are installed and available at the EADM interface ofthe machine model where the software is running and are available to theSAP and software to take advantage of those installed set of functionsof the set of instructions. Thus, a specified EADM command is installedand available only if the required EADM feature is installed andavailable where the software is running as well as the required set offunctions of the set of instructions that the specified EADM commanduses to complete the specified EADM command are also indicated to beinstalled and available where the software is running based on the EADMsub-functions flag(s) that include those set of functions of the set ofinstructions.

If the EADM sub-functions flag is not set, the process flow 2100proceeds to block 2160 (as indicated by the NO arrow). That is, the setof functions of the set of instructions that are represented by thatEADM sub-functions flag are not installed on the machine model where thesoftware is running and cannot be used by the SAP or software.

The technical effects and benefits of embodiments herein allow new EADMcommands that belong to an existing EADM feature and to be added to anexisting EADM feature without requiring a new EADM feature for the newEADM commands. Therefore, embodiments herein provide better features,instructions and functions grouping, uses less functions definitionspace, simplifies hardware, SAP and software design, and reduceshardware, SAP and software processing time to determine the EADMcommands validity.

For example, the availability of the new CPU Deflate-Compression-Call(DFLTCC) instruction with specific functions are controlled by a newDeflate-Compression facility bit (flag) and each configured CPU in themachine can access them directly via the CPU interface. But EADMfacility (the second machine architecture) uses the I/O subsystem(second machine) interface to also execute the same DFLTCC instructionwith a subset of functions via the SAP using its own separate commandnames, mnemonic and code to accomplish a task. The software cannotcommunicate with the SAPs directly from a CPU (needs I/O subsysteminterface) thus the software does not have a way to find out if specificfunctions of the DFLTCC instruction are installed and available via theEADM facility.

The EADM-compression feature is defined as a generic compression featurewhich can include different types of compression algorithms. Itcurrently provides deflate-compression algorithm support. MultipleEADM-Deflate-Compression commands are defined to perform compress anddecompress operations using one or more deflate-compression functions.However, the EADM compression feature does not specify if any one of theEADM-Deflate-Compression commands are valid; instead, it specifies thatall the EADM-Deflate-Compression commands are supported.

Various embodiments of the invention are described herein with referenceto the related drawings. Alternative embodiments of the invention can bedevised without departing from the scope of this invention. Variousconnections and positional relationships (e.g., over, below, adjacent,etc.) are set forth between elements in the following description and inthe drawings. These connections and/or positional relationships, unlessspecified otherwise, can be direct or indirect, and the presentinvention is not intended to be limiting in this respect. Accordingly, acoupling of entities can refer to either a direct or an indirectcoupling, and a positional relationship between entities can be a director indirect positional relationship. Moreover, the various tasks andprocess steps described herein can be incorporated into a morecomprehensive procedure or process having additional steps orfunctionality not described in detail herein.

The following definitions and abbreviations are to be used for theinterpretation of the claims and the specification. As used herein, theterms “comprises,” “comprising,” “includes,” “including,” “has,”“having,” “contains” or “containing,” or any other variation thereof,are intended to cover a non-exclusive inclusion. For example, acomposition, a mixture, process, method, article, or apparatus thatcomprises a list of elements is not necessarily limited to only thoseelements but can include other elements not expressly listed or inherentto such composition, mixture, process, method, article, or apparatus.

Additionally, the term “exemplary” is used herein to mean “serving as anexample, instance or illustration.” Any embodiment or design describedherein as “exemplary” is not necessarily to be construed as preferred oradvantageous over other embodiments or designs. The terms “at least one”and “one or more” may be understood to include any integer numbergreater than or equal to one, i.e. one, two, three, four, etc. The terms“a plurality” may be understood to include any integer number greaterthan or equal to two, i.e. two, three, four, five, etc. The term“connection” may include both an indirect “connection” and a direct“connection.”

The terms “about,” “substantially,” “approximately,” and variationsthereof, are intended to include the degree of error associated withmeasurement of the particular quantity based upon the equipmentavailable at the time of filing the application. For example, “about”can include a range of ±8% or 5%, or 2% of a given value.

For the sake of brevity, conventional techniques related to making andusing aspects of the invention may or may not be described in detailherein. In particular, various aspects of computing systems and specificcomputer programs to implement the various technical features describedherein are well known. Accordingly, in the interest of brevity, manyconventional implementation details are only mentioned briefly herein orare omitted entirely without providing the well-known system and/orprocess details.

The present invention may be a system, a method, and/or a computerprogram product at any possible technical detail level of integration.The computer program product may include a computer readable storagemedium (or media) having computer readable program instructions thereonfor causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, configuration data for integrated circuitry, oreither source code or object code written in any combination of one ormore programming languages, including an object oriented programminglanguage such as Smalltalk, C++, or the like, and procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The computer readable program instructions may executeentirely on the user's computer, partly on the user's computer, as astand-alone software package, partly on the user's computer and partlyon a remote computer or entirely on the remote computer or server. Inthe latter scenario, the remote computer may be connected to the user'scomputer through any type of network, including a local area network(LAN) or a wide area network (WAN), or the connection may be made to anexternal computer (for example, through the Internet using an InternetService Provider). In some embodiments, electronic circuitry including,for example, programmable logic circuitry, field-programmable gatearrays (FPGA), or programmable logic arrays (PLA) may execute thecomputer readable program instructions by utilizing state information ofthe computer readable program instructions to personalize the electroniccircuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the blocks may occur out of theorder noted in the Figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiments. The terminology used herein was chosen to best explain theprinciples of the embodiments, the practical application, or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the embodimentsdisclosed herein.

What is claimed is:
 1. A method comprising: defining, by a processor ofa computer, a sub-functions field in a response block of a call command,the processor communicatively coupled to a memory, the response blockbeing stored in the memory; wherein the call command comprises a storeextended asynchronous data mover (EADM) information channel subsystemcall (CHSC); wherein the response block comprises an EADM sub-functionflags field; and wherein each bit in the EADM sub-functions flags fieldrepresents one function of a set of functions that are installed andavailable at an interface.
 2. The method of claim 1 further comprisingindicating, by the processor, the set of functions that are installedand available at the interface based on a corresponding sub-functionsflag within the EADM sub-functions flags field being set, the interfacebeing executed on the computer, the set of functions being representedby the EADM sub-functions flags field.
 3. The method of claim 2 furthercomprising: indicating, by the processor, the set of functions of theset of instructions are not installed based on the correspondingsub-functions flag not being set.
 4. The method of claim 1, wherein theinterface comprises an EADM interface.
 5. The method of claim 1, whereinthe set of functions of the set of instructions are of a first machinebeing executed on the computer, and wherein the interface is a secondmachine.
 6. The method of claim 1, wherein the set of functions are notusable by the interface based on the set of functions of the set ofinstructions represented by the EADM sub-functions flag not beinginstalled.
 7. The method of claim 1, wherein a facility uses theinterface to execute the set of instructions with a subset of functionsvia a system assistance processor of the computer.
 8. The method ofclaim 7, wherein the facility contains a set of managing EADM featuresand each one of these features includes a set of EADM commands.
 9. Themethod of claim 8, wherein each command of the set of EADM commands canuses one or more of the set of instructions and corresponding functionsto complete a task.
 10. A computer program product comprising a computerreadable storage medium, the computer readable storage medium comprisingcomputer executable instructions, which when executing by a processor ofa computer causes operations comprising: defining, by the processor, asub-functions field in a response block of a call command, the processorcommunicatively coupled to a memory, wherein the call command comprisesa store extended asynchronous data mover (EADM) information channelsubsystem call (CHSC), wherein the response block comprises an EADMsub-function flags field, the response block being stored in the memory,wherein each bit in the EADM sub-functions flags field represents onefunction of a set of functions that are installed and available at aninterface; indicating, by the processor, the set of functions that areinstalled and available at the interface based on a correspondingsub-functions flag within the EADM sub-functions flags field being set,the interface being executed on the computer, the set of functions beingrepresented by the EADM sub-functions flags field; and indicating, bythe processor, the set of functions of the set of instructions are notinstalled based on the corresponding sub-functions flag not being set.11. The computer program product of claim 10, wherein the interfacecomprises an EADM interface.
 12. The computer program product of claim10, wherein the set of functions of the set of instructions are of afirst machine being executed on the computer, and wherein the interfaceis a second machine.
 13. The computer program product of claim 10,wherein the set of functions are not usable by the interface based onthe set of functions of the set of instructions represented by the EADMsub-functions flag not being installed.
 14. The computer program productof claim 10, wherein a facility uses the interface to execute the set ofinstructions with a subset of functions via a system assistanceprocessor of the computer.
 15. The computer program product of claim 14,wherein the facility contains a set of managing EADM features and eachone of these features includes a set of EADM commands.
 16. The computerprogram product of claim 15, wherein each command of the set of EADMcommands uses one or more of the set of instructions and correspondingfunctions to complete a task.
 17. A system comprising: an interfacebeing executed thereon; a memory storing a response block; and aprocessor communicatively coupled to the memory and causing operationsof the system comprising: defining, by the processor, a sub-functionsfield in the response block of the call command, wherein the callcommand comprises a store extended asynchronous data mover (EADM)information channel subsystem call (CHSC), wherein the response blockcomprises an EADM sub-function flags field, the processorcommunicatively coupled to a memory, wherein each bit in the EADMsub-functions flags field represents one function of a set of functionsthat are installed and available at an interface.
 18. The system ofclaim 17 further comprising: indicating, by the processor, the set offunctions that are installed and available at the interface based on acorresponding sub-functions flag within the EADM sub-functions flagsfield being set, the interface being executed on the computer, the setof functions being represented by the EADM sub-functions flags field;and indicating, by the processor, the set of functions of the set ofinstructions are not installed based on the corresponding sub-functionsflag not being set.
 19. The system of claim 17, wherein thesub-functions field comprises an EADM sub-functions field.
 20. Thesystem of claim 17, wherein the call command comprises an EADMinformation channel subsystem call command.